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 reference that does not inherit future changes from the source unless explicitly refreshed. Branches do not inherit future changes from source? > * Branches maintain a complete history of changes and allow commits, merges, and rollbacks, whereas shallow clones are meant for lightweight table duplication without maintaining lineage. Branches don't maintain the complete history, they are essentially just a tag in the metadata.json and while they can allow for other operations to be performed on top of them I'm not sure how that's different than a shallow clone. > * Shallow clones focus on quick duplication of datasets for different workloads (e.g., testing, experimentation) without affecting the original table structure, unlike branches that are designed for collaborative versioning and long-term dataset evolution. What stops a branch being used for testing or experimentation? How would this effect the original table? -- 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
