CTTY opened a new pull request, #3704:
URL: https://github.com/apache/iceberg-rust/pull/3704

   
   
   ## Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   - Closes #.
   
   ## What changes are included in this PR?
   
   An engine that splits a data file into several read tasks must cut on the 
row-group boundaries the writer recorded as `split_offsets` (spec field 132), 
or a split can land inside a row group and one of the two tasks opens the file 
for nothing. `FileScanTask` had no way to hand them on, so an engine planning 
with iceberg-rust had to split arithmetically.
   
   - `FileScanTask::split_offsets: Option<Vec<i64>>`, builder default, 
accessor, serde in both directions; `None` when the writer recorded none.
   - Populated from the manifest entry's `DataFile` in `ManifestEntryContext:: 
into_file_scan_task`.
   - `TableTestFixture::setup_manifest_files_with_split_offsets` and a scan 
test covering recorded, empty and absent offsets; the serde round-trip test 
carries the field.
   
   <!--
   Provide a summary of the modifications in this PR. List the main changes 
such as new features, bug fixes, refactoring, or any other updates.
   -->
   
   ## Are these changes tested?
   - Added unit tests
   <!--
   Specify what test covers (unit test, integration test, etc.).
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   
   ## AI Disclosure
   Used claude
   <!--
   
https://iceberg.apache.org/contribute/#guidelines-for-ai-assisted-contributions
   -->
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to