-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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-18253: [C++][Parquet] Add additional bounds safety checks #14592
Conversation
|
Is this something that can happen due to bad user input? Or are you simply checking for internal invariants? |
A little bit of both. The only one as far as I can determine that would be a function of bad parquet files is the overflow when down-casting. But I think there are other safe guard in place here. In terms of bad user input, if we are talking about code that consumes these libraries I think most of the places do the negative checks are guards against here (the one exception being PathWriter), which I believe is completely internal. These were raised by another team doing a code audit and "yellow flags". If any of them strike you as superfluous I can revert them. |
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
Benchmark runs are scheduled for baseline = 28a1152 and contender = 147b5c9. 147b5c9 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
No description provided.