Invalid bitpacking mode

[Adisekharp]

java.sql.SQLException: INTERNAL Error: Invalid bitpacking mode
This error signals an assertion failure within DuckDB. This usually occurs due to unexpected conditions or errors in the program's logic.
can anyone help on this?

[staticlibs]

@Adisekharp

Yes, I can investigate it. Can you provide any details how this can be reproduced?

[Adisekharp]

Firstly i perform some operation in .db file
then closing the connection with .db file
after that i opened mother duck connection then attached the above .db file to the motherduck connection
after performing some operation with motherduck, again i reopen the file connection with duckdb then trying to perform some operation then this issue occurs.
Note:- I am using duckdb jar 1.1.3v

[staticlibs]

@Adisekharp

Thanks for the details! Can you clarify, whether the database file becomes permanently corrupted after it is opened with DuckDB and issue occurs? Or is the issue intermittent (after it is happened)?

Also, does the issue happen on reading (SELECT) or writing data? Does the code, that is doing the operations on the DB file from Java, uses multithreading, and if "yes" - then in what way?

[staticlibs]

@Adisekharp

I've experimented with attaching a local DB to MotherDuck, I wonder if you can check the example here to give any hints which workload to add there (updates, multi-threading etc) to make it similar to the actual workload with which the problem happens?

For now I can only assume that the DB file is getting corrupted somehow when being attached/detached between the connections.