-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Arrow] Properly use the parent's array.offset
in many places in the scan
#9661
Conversation
…ssues looking at the patterns of the previous fixes
…dition mather | abstract the offset away into GetEffectiveOffset
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks great. Could you just look at the failing CI?
Weirdly that's one of the tests I added, seems I didn't run it - and it was broken Discovered another bug concerning dictionaries, structs and nulls - |
Had this weird CI failure on my fork:
Probably caused by this being the version of the installed package:
|
Thanks! |
Merge pull request duckdb/duckdb#9661 from Tishj/arrow_parent_offsets Merge pull request duckdb/duckdb#9686 from ywelsch/yw/dbgen-schema-in-other-catalog Merge pull request duckdb/duckdb#9674 from szarnyasg/replace-old-logos
This PR fixes #5547
It seems like the arrow arrays hit a certain chunk size limit, and are split up over multiple arrays while sharing the same buffer.
These offsets are put onto the struct array and should be forwarded to the child arrays, we did not do this previously.
(Or at least not consistently)