GH-15173: [C++][Parquet] Fixing ByteStreamSplit Standard broken#34140
GH-15173: [C++][Parquet] Fixing ByteStreamSplit Standard broken#34140wjones127 merged 3 commits intoapache:mainfrom
Conversation
|
@pitrou @wgtmac @wjones127 PTAL |
7fff3fb to
3e6550c
Compare
wjones127
left a comment
There was a problem hiding this comment.
Looks good. Just one suggestion on the exception description.
|
Comment fixed |
|
Benchmark runs are scheduled for baseline = 8e5e438 and contender = c31fb46. c31fb46 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
…amSplitDecoder (#41565) ### Rationale for this change This problem is raised from #40094 . Original bug fixed here: #34140 , but this is corrupt in #40094 . ### What changes are included in this PR? Refine checking ### Are these changes tested? * [x] Will add ### Are there any user-facing changes? Bugfix * GitHub Issue: #41562 Authored-by: mwish <maplewish117@gmail.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
…amSplitDecoder (#41565) ### Rationale for this change This problem is raised from #40094 . Original bug fixed here: #34140 , but this is corrupt in #40094 . ### What changes are included in this PR? Refine checking ### Are these changes tested? * [x] Will add ### Are there any user-facing changes? Bugfix * GitHub Issue: #41562 Authored-by: mwish <maplewish117@gmail.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
…teStreamSplitDecoder (apache#41565) ### Rationale for this change This problem is raised from apache#40094 . Original bug fixed here: apache#34140 , but this is corrupt in apache#40094 . ### What changes are included in this PR? Refine checking ### Are these changes tested? * [x] Will add ### Are there any user-facing changes? Bugfix * GitHub Issue: apache#41562 Authored-by: mwish <maplewish117@gmail.com> Signed-off-by: Antoine Pitrou <antoine@python.org>
Rationale for this change
This patch fixes bugs in BYTE_STREAM_SPLIT. It enforce the parquet ByteStreamSplit not to use padding, and force using
sizeof(data) / sizeof(T)as num-of-values.What changes are included in this PR?
Are these changes tested?
Yes
Are there any user-facing changes?
No