Closed cocoa-xu closed 3 weeks ago
Hi @felipecrv, many thanks for the code review and these examples! I've adapted some code from the code snippets in the review, and it should handle the validation properly now. :)
Attention: Patch coverage is 69.56522%
with 28 lines
in your changes missing coverage. Please review.
Project coverage is 88.55%. Comparing base (
8894ebf
) to head (0ce34e5
). Report is 10 commits behind head on main.
Files | Patch % | Lines |
---|---|---|
src/nanoarrow/array.c | 55.55% | 28 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Just added more tests to cover more lines and the memory issue in the schema test should be fixed.
Just a few nits, but this looks good from my end!
@felipecrv are there any more REE-specific details relevant to this PR (or follow-ups that we need to open issues for and tackle before the next release?)
Not that I'm aware right now. I recommend that you and @cocoa-xu take a look at the C++ code around REEs to see all the traps. I don't remember everything that I did, but I left many comments in the C++ implementation.
https://github.com/apache/arrow/blob/main/cpp/src/arrow/util/ree_util.h and https://github.com/apache/arrow/blob/main/cpp/src/arrow/util/ree_util.cc are good sources to look at.
I think this PR introduced a regression that valgrind is complaining about. You can see it started back in the weekly Meson build:
https://github.com/apache/arrow-nanoarrow/actions/runs/9432588616
A more detailed error description can be found here:
https://github.com/apache/arrow-nanoarrow/actions/runs/9457996609/job/26052769002?pr=483#step:7:319
Apparently Valgrind does not like something that ultimately hits this codeblock from the RunEndEncoded tests:
Hi this PR tries to add support for run-end encoded array based on the arrow spec here, https://arrow.apache.org/docs/format/Columnar.html#run-end-encoded-layout.