c-thiel opened a new issue, #733: URL: https://github.com/apache/iceberg-rust/issues/733
The general philosophy of any engine that implements Iceberg-Rust is that they should not care about things like field-IDs / source-ids. Therefore we try to hide this logic behind APIs. To allow evolution of the sort orders, we have the [UpdateSpec API in Python](https://github.com/apache/iceberg-python/blob/4b96d2f49b04ff7ec551646f489ecc50ac195b5d/pyiceberg/table/__init__.py#L3003) and the [BaseUpdatePartitionSpec (implements UpdatePartitionSpec) in Java](https://github.com/apache/iceberg/blob/163e2068f96f139632488f36928bf443c9be326f/core/src/main/java/org/apache/iceberg/BaseUpdatePartitionSpec.java#L44). Mutating partition specs works differently in V1 and V2 of the spec. I think it would be OK to focus on V2 first and simply fail to write V1 for now. @liurenjie1024, @Xuanwo do you agree or is mutation / write for V1 important? -- 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: issues-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
