Skip to content
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

Merged
merged 4 commits into from
Nov 9, 2022

Conversation

emkornfield
Copy link
Contributor

No description provided.

@emkornfield emkornfield requested a review from pitrou November 5, 2022 00:12
@github-actions
Copy link

github-actions bot commented Nov 5, 2022

@github-actions
Copy link

github-actions bot commented Nov 5, 2022

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@pitrou
Copy link
Member

pitrou commented Nov 5, 2022

Is this something that can happen due to bad user input? Or are you simply checking for internal invariants?

@emkornfield
Copy link
Contributor Author

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>
@pitrou pitrou changed the title ARROW-18253: Add additional bounds safety checks ARROW-18253: [C++][Parquet] Add additional bounds safety checks Nov 9, 2022
@pitrou pitrou merged commit 147b5c9 into apache:master Nov 9, 2022
@ursabot
Copy link

ursabot commented Nov 10, 2022

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.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.3% ⬆️0.03%] test-mac-arm
[Finished ⬇️0.0% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 147b5c92 ec2-t3-xlarge-us-east-2
[Finished] 147b5c92 test-mac-arm
[Finished] 147b5c92 ursa-i9-9960x
[Finished] 147b5c92 ursa-thinkcentre-m75q
[Finished] 28a1152a ec2-t3-xlarge-us-east-2
[Finished] 28a1152a test-mac-arm
[Finished] 28a1152a ursa-i9-9960x
[Finished] 28a1152a ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants