jbewing opened a new pull request, #14683:
URL: https://github.com/apache/iceberg/pull/14683

   This PR updates all writes from Spark 4.0 & 3.5 to set the `sort_order_id` 
of data files when applicable per the [Iceberg Table 
Spec](https://iceberg.apache.org/spec/#partition-evolution:~:text=A%20data%20or%20delete%20file%20is%20associated%20with%20a%20sort%20order%20by%20the%20sort%20order%27s%20id%20within%20a%20manifest).
 I've opened this PR to:
   1. Gauge interest in this and validate my approach
   2. If the approach is good, make a decision on whether to backport these 
changes to Spark 3.4. This patch doesn't apply super cleanly to 3.4 as it 
stands right now, so I don't want to invest effort into it unless others would 
find value from it.
   3. As a follow up to those PRs, implement the ability to then report this 
ordering information when applicable to Spark to better inform the query 
planner of potential optimizations. This is rather useful when used in 
conjunction with SPJ and I have this running on an Iceberg fork with success
   
   This is a successor to my initial PR 
https://github.com/apache/iceberg/pull/13636 which has since been closed for 
being stale (but I've revived it here and ported the changes forwards to spark 
4.0). I've re-opened this PR as of late there has been some increased interest 
in this:
   - A community member has expressed interest in reviving my older PR 
https://github.com/apache/iceberg/pull/13636#issuecomment-3505090324
   - Other community members have reported this same bug on the issue list 
https://github.com/apache/iceberg/issues/14531 
   
   So it appears that there is value to these changes being upstreamed instead 
of confined to a fork.
   
   ### Testing
   I've added tests for newer added utility functions and updated existing 
tests that write data files and compact data files in a sorted manner to verify 
that we're setting the `sort_order_id` entry in the manifests to the correct 
value. Additionally, I've used this patch on an internal fork and verified that 
it correctly sets this field during compaction and normal writes.
   
   Issue: https://github.com/apache/iceberg/issues/13634


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