-
Notifications
You must be signed in to change notification settings - Fork 3.8k
GH-46659: [C++] Fix export of extension arrays with binary view/string view storage #46660
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
GH-46659: [C++] Fix export of extension arrays with binary view/string view storage #46660
Conversation
|
@bkietz Any chance you have a minute to ensure I understood this correctly? |
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.
This looks right to me, just a few nits
Co-authored-by: Benjamin Kietzman <bengilgit@gmail.com>
Co-authored-by: Benjamin Kietzman <bengilgit@gmail.com>
Thank you for the review! |
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 610c201. There were 70 benchmark results with an error:
There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 4 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
Extension arrays exported with binary view/string view storage did not export the variadic sizes buffer which resulted in crashes when reimporting.
What changes are included in this PR?
The expression that controlled whether the variadic sizes buffer was written was updated.
Are these changes tested?
Yes, a test was added
Are there any user-facing changes?
No