MonkeyCanCode opened a new pull request, #16521: URL: https://github.com/apache/iceberg/pull/16521
## Background After upgraded Apache Iceberg runtime from 1.10.1 to 1.11.0, the write from spark on my workload started to fail when the table has a historical sort order that references a column that has since been dropped from the schema. This is introduced by https://github.com/apache/iceberg/pull/15150. This is also reported by @aihuaxu via https://github.com/apache/iceberg/issues/16519 ## Change `SerializableTable.sortOrders()` strict binds every sort order against the current schema, which fails when a historical sort order references a field dropped by schema evolution. This PR fixes it to only strict bind the default sort order. ## Test Plan I added the new test case added by @aihuaxu from https://github.com/apache/iceberg/issues/16519 as well as the local reproducible that I wrote to validate the issue is resolved by this PR. -- 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]
