RussellSpitzer commented on issue #12263:
URL: https://github.com/apache/iceberg/issues/12263#issuecomment-2667530132
Only 1 is a difference here and it's at the catalog level. A branch cannot
affect files in another branch. If you delete a snapshot from 1 branch but it
still exists in anot
RussellSpitzer commented on issue #12263:
URL: https://github.com/apache/iceberg/issues/12263#issuecomment-2667481681
Again, how is this different than a branch? Are you just saying you want a
branch with a different catalog identifier?
--
This is an automated message from the Apache Git
databius commented on issue #12263:
URL: https://github.com/apache/iceberg/issues/12263#issuecomment-2667369068
> What are we looking for here that doesn't exist within branching?
My case copying production data to a separate environment. Example:
```
CREATE TABLE myproject.m
RussellSpitzer commented on issue #12263:
URL: https://github.com/apache/iceberg/issues/12263#issuecomment-2663873430
I don't follow these points
> * Branching creates an isolated version of a table's metadata that can
diverge over time, while shallow cloning creates a new table refer
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.
