Error: INTERNAL Error: Unsupported compression function type

[xelephas]

What happens?

I am getting this error when running a simple select query on a user uploaded duckdb database file:

Error: INTERNAL Error: Unsupported compression function type
    at pa.runQuery (duckdb-browser-eh.worker.js:1:741917)
    at Lo.onMessage (duckdb-browser-eh.worker.js:1:729928)
    at Bc.globalThis.onmessage (duckdb-browser-eh.worker.js:1:763450)
@duckdb_duckdb-wasm.js?v=597ea27d:11971 Uncaught (in promise) Error: INTERNAL Error: Unsupported compression function type
    at O.onMessage (@duckdb_duckdb-wasm.js?v=597ea27d:11971:15)

To Reproduce

 await db.registerFileHandle(
            "data_file.duckdb",
            file, // user uploaded file
            2,
            true
        );

const conn = await db.connect();
await conn.query("ATTACH 'data_file.duckdb'")
const arrowResult = await conn.query('select * from data_file.AAPL')

Browser/Environment:

Chrome, Version 126.0.6478.127 (Official Build) (arm64)

Device:

MacOS

DuckDB-Wasm Version:

1.28.1-dev106.0

DuckDB-Wasm Deployment:

Local development

Full Name:

William Walker

Affiliation:

Individual

[elsbrock]

Experiencing the same, but loading the file via ATTACH 'https://.... File can be opened just fine via duckdb CLI.

Edit: figured it out; anything other than uncompressed or none is not supported; you can force the format with PRAGMA force_compression. I tried rle, dictionary, pfor, bitpacking and fsst (not sure if there's more).

[carlopi]

I think this is not expected, could either of you possibly share a DB file that demonstrates this problem?

[elsbrock]

I think it depends on the bundle that was used. I changed it to the Vite approach, and I haven't seen those errors anymore.

[xelephas]

Thank you @carlopi for looking into this.

Here is the sample file:

https://file.io/PNwQR8qqgict

[marian-andre]

Hello ! I got the same behavior and the same error.
Unfortunately, I cannot share the .duckdb file
One hint from my side: if we use force_compression=uncompressed, no issue anymore. But it's not convenient for me as the file size is huge

EDIT: Installing the module from npm installs the version 1.28.1-dev106.0, with which I get the issue.
By forcing a newer version, for example 1.28.1-dev258.0, I don't get the issue at all.