amogh-jahagirdar edited a comment on pull request #4071:
URL: https://github.com/apache/iceberg/pull/4071#issuecomment-1035985498
@rdblue I will also need to think more on this as well. I think ultimately
if we work backwards from:
1.) cherryPickAll(String destinationBranch, String sourceBranch) is a
useful operation to perform for Iceberg users to perform (which I think it is,
I envision workflows which can benefit from being able to cherry-pick snapshots
from one lineage to another)
2.) Given 1, and the fact that cherryPickAll does a cherry pick of
individual snapshots in an atomic manner across all snapshots, I don't see an
obvious way around using a transaction.
After looking more at ManageSnapshots, I do agree that likely it could be
combined with UpdateSnapshotRefs (with the APIs you mentioned), but don't see a
way around using the existing transaction abstraction. Perhaps there is a
better model here though.
@rdblue For my understanding, is there a reason we are trying to avoid a
transaction? Is it mostly for simplicity in the API?
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
