Apache Iceberg version
main (development)
Please describe the bug 🐞
Right now, updateSpec reads table state and schema exclusively from the immutable table snapshot captured when the transaction started instead of the transaction's staged metadata.
As a result, partition evolution cannot see columns or specs added earlier in the same txn.
What is expected? Any chained operation should succeed, binding any new col against the transaction's staged schema.
Contribution
Will raise a PR with the fix
Apache Iceberg version
main (development)
Please describe the bug 🐞
Right now,
updateSpecreads table state and schema exclusively from the immutable table snapshot captured when the transaction started instead of the transaction's staged metadata.As a result, partition evolution cannot see columns or specs added earlier in the same txn.
What is expected? Any chained operation should succeed, binding any new col against the transaction's staged schema.
Contribution
Will raise a PR with the fix