Glob partitioning causes wasm exception

[danthegoodman1]

What happens?

When using the query SELECT count(*) FROM read_parquet('s3://ookla-open-data/parquet/performance/type=fixed/year=2022/quarter=1/*.parquet', HIVE_PARTITIONING = 1, filename=true); in the wasm shell, it throws an exception. This query runs fine in python duckdb.

To Reproduce

duckdb> SELECT count() FROM read_parquet('s3://ookla-open-data/parquet/performance/type=fixed/year=2022/quarter=1/.parquet', HIVE_PARTITIONING = 1, filename=true);

Invalid Error: [object WebAssembly.Exception]

Browser/Environment:

Chrome 110

Device:

mbp 2019 16inch

DuckDB-Wasm Version:

SELECT count() FROM read_parquet('s3://ookla-open-data/parquet/performance/type=fixed/year=2022/quarter=1/.parquet', HIVE_PARTITIONING = 1, filename=true);

DuckDB-Wasm Deployment:

shell.duckdb.org

Full Name:

Dan Goodman

Affiliation:

Self

[uadjet]

Having this same issue across multiple browsers and deployments.

[murrayju]

I want to echo that I'm having the same problem. Any plan to fix this?

[rickiesmooth]

I think this is related to https://github.com/duckdb/duckdb-wasm/issues/1040

[carstonhernke]

This would be great to get working - I'm happy to help where I can. If the issue is with the httpfs extension, is this something that the upcoming updates to extension loading will affect? Any hints would be appreciated so I know where to start poking. @carlopi