Fokko commented on issue #12263: URL: https://github.com/apache/iceberg/issues/12263#issuecomment-2662578382
> Future writes to the cloned table should create new data files, without affecting the source table. I don't think that's an issue, all the (meta)data in Iceberg is immutable. What could happen is that the original table progresses, and at some point, the snapshot that the other table cloned off will expire. This will then break the cloned table. This is something that we need to figure out as part of the location ownership https://github.com/apache/iceberg/issues/9133 I agree with @RussellSpitzer that this is very similar to branching, and it also overlaps with creating a view of a specific version of the table. > unlike branches that are designed for collaborative versioning and long-term dataset evolution. Branches are pretty flexible, and I think it could also work for your use-case here. For example, see [write-audit-publish](https://www.tabular.io/blog/integrated-audits/). -- 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 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
