-
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
GH-38071: [C++][CI] Fix Overlap column chunk ranges for pre-buffer #38073
Conversation
|
@jorisvandenbossche @lidavidm I've add an |
std::vector<ReadRange> CoalesceReadRanges(std::vector<ReadRange> ranges, | ||
int64_t hole_size_limit, | ||
int64_t range_size_limit); | ||
Result<std::vector<ReadRange>> CoalesceReadRanges(std::vector<ReadRange> ranges, |
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.
Don't know if this matter, since it change the public api.
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.
It's in an internal
header so no expectation that it remains stable
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.
Oh, that's good, thanks!
Hmm...Seems this is not caused by me 🤔 |
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.
+1
The Azure failure will be unrelated. I re-ran the job.
I've rebase the master to rerun the test :-) Hope this time it passes... |
Passed. :-) |
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 0b9f817. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Thanks a lot @mapleFU for fixing this! |
…fer (apache#38073) ### Rationale for this change The C++ Parquet Arrow fuzz will generate bad Parquet file with bad row-range, this patch change the `CoalesceReadRanges` to return `Result<>`. ### What changes are included in this PR? Just a checking, change `CoalesceReadRanges` to return `Result<>`. ### Are these changes tested? No. ### Are there any user-facing changes? No. * Closes: apache#38071 Authored-by: mwish <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…fer (apache#38073) ### Rationale for this change The C++ Parquet Arrow fuzz will generate bad Parquet file with bad row-range, this patch change the `CoalesceReadRanges` to return `Result<>`. ### What changes are included in this PR? Just a checking, change `CoalesceReadRanges` to return `Result<>`. ### Are these changes tested? No. ### Are there any user-facing changes? No. * Closes: apache#38071 Authored-by: mwish <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…fer (apache#38073) ### Rationale for this change The C++ Parquet Arrow fuzz will generate bad Parquet file with bad row-range, this patch change the `CoalesceReadRanges` to return `Result<>`. ### What changes are included in this PR? Just a checking, change `CoalesceReadRanges` to return `Result<>`. ### Are these changes tested? No. ### Are there any user-facing changes? No. * Closes: apache#38071 Authored-by: mwish <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Rationale for this change
The C++ Parquet Arrow fuzz will generate bad Parquet file with bad row-range, this patch change the
CoalesceReadRanges
to returnResult<>
.What changes are included in this PR?
Just a checking, change
CoalesceReadRanges
to returnResult<>
.Are these changes tested?
No.
Are there any user-facing changes?
No.