Segfaults even with duckdb v0.7+ installed

[jrabary]

Hi,
I'm giving lance a try and get segfaults even with duckedb v0.7.1. I'm using Mac OS with m1 chips.
Any ideas ?

[changhiskhan]

Can you help us repro it? What's the data / query look like?

[jrabary]

I've just find out why I get this. I have a large parquet file with binary image inside. Generated from coco dataset. When I run a query with duckdb.query("SELECT * ...") I get a segfault. But if I specify a column like "SELECT image ..." it works.

[changhiskhan]

Would you be able to share the data?

1. If you do "SELECT * EXCLUDE(image) ...", do you still get a segfault? If so, can you share the parquet dataset without the image column (hopefully making it much smaller) ?
2. OR if like the first 10 rows still reproduces the error, just share the first 10 rows?

Another possibility is that we're working on #664 which adds support for list-of-dict or list-of-struct-with-dict fields. If you've converted data from parquet, it's possible this is the problem too.

If you can, please share the data so we can verify it from our end before the next release

[jrabary]

Not sure whether this is an issue anymore. Maybe our parquet file was not correctly generated