lyne7-sc opened a new pull request, #3479:
URL: https://github.com/apache/iceberg-rust/pull/3479

   ## 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 #3475.
   
   ## What changes are included in this PR?
   
   <!--
   Provide a summary of the modifications in this PR. List the main changes 
such as new features, bug fixes, refactoring, or any other updates.
   -->
   
   Reading older Parquet files after column renames can silently return values 
under the wrong columns when the projection changes their order and the 
corresponding types and nullability match. For example, projecting `[y#2, x#1]` 
from `[a#1=10, b#2=20]` can return `[10, 20]` instead of `[20, 10]`.
   
   Require field IDs to match at each position before passing a batch through 
or updating only its schema. Otherwise, use the existing field-ID-based 
transformation. This also prevents treating a same-name field with a new ID as 
the original field.
   
   ## Are these changes tested?
   
   <!--
   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)?
   -->
   
   - Transformer tests cover reordered renamed columns, cached plan reuse, and 
same-name fields with different IDs.
   - `test_renamed_reverse_projection_reads_values_by_field_id` verifies the 
projected values and schema when reading a local Parquet file.
   
   ## AI Disclosure
   
   <!--
   
https://iceberg.apache.org/contribute/#guidelines-for-ai-assisted-contributions
   -->
   
   Developed with assistance from OpenAI Codex.


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