Since yesterday we've noticed an issue with the PyIceberg CI when we do integration testing with PyIceberg:
@pytest.mark.integration
def test_duckdb_url_import(warehouse: Path, arrow_table_with_null: pa.Table) -> None:
os.environ["TZ"] = "Etc/UTC"
time.tzset()
tz = pytz.timezone(os.environ["TZ"])
catalog = SqlCatalog("test_sql_catalog", uri="sqlite:///:memory:", warehouse=f"/{warehouse}")
catalog.create_namespace("default")
identifier = "default.arrow_table_v1_with_null"
tbl = _create_table(catalog, identifier, {}, [arrow_table_with_null])
location = tbl.metadata_location
import duckdb
duckdb.sql("INSTALL iceberg; LOAD iceberg;")
> result = duckdb.sql(
f"""
SELECT *
FROM iceberg_scan('{location}')
"""
).fetchall()
E duckdb.duckdb.InvalidInputException: Invalid Input Error: Function with name "read_avro" not found in ExtensionUtil::GetTableFunction
Does this sounds a bell?
Since yesterday we've noticed an issue with the PyIceberg CI when we do integration testing with PyIceberg:
Does this sounds a bell?