lxy-9602 opened a new pull request, #231:
URL: https://github.com/apache/paimon-cpp/pull/231

   <!-- PR titles must follow Conventional Commits: <type>(<optional-scope>): 
<description> -->
   
   ### Purpose
   
   <!-- Linking this pull request to the issue -->
   Linked issue: #197 
   
   Backport Arrow community fixes for nullable `FixedSizeList` Parquet 
read/write:
   
   - Writer: support child values split by null list slots.
   - Reader: pad null slots before constructing `FixedSizeListArray`.
   - Remove Paimon's Parquet-specific VECTOR write conversion and write through 
Arrow directly.
   
   The backport follows Arrow's current implementation, with only a C++17 
`arrow::util::span`
   adaptation for Arrow 17.
   
   Related: apache/arrow#35692, apache/arrow#35697, apache/arrow#50271.
   
   <!-- What is the purpose of the change -->
   
   ### Tests
   
   - Nullable and all-null FixedSizeList round trips.
   - Nullable Java LIST and Rust FixedSizeList fixtures.
   - Mixed Java/Rust file reads.
   - Nested VECTOR and predicate pushdown.
   
   <!-- List UT and IT cases to verify this change -->
   
   ### API and Format
   
   <!-- Does this change affect API in include dir or storage format or 
protocol -->
   
   ### Documentation
   Updated the VECTOR compatibility fixture documentation.
   
   <!-- Does this change introduce a new feature -->
   
   ### Generative AI tooling
   Generated-by: Codex (GPT-5)
   <!--
   If generative AI tooling has been used in the process of authoring this 
patch, please include the
   phrase: 'Generated-by: ' followed by the name of the tool and its version.
   If no, write 'No'.
   Please refer to the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to