Mint a new generation when compose overwrites an object - #2324
Open
gaul wants to merge 1 commit into
Open
Conversation
ComposeObject reused the destination's generation, so composing over an existing object on a versioning-enabled bucket archived the old copy and stored the new one under the same generation: a versioned listing showed two entries sharing an id, and the archived copy was no longer addressable on its own. Cloud Storage gives a compose result a new generation like any other write; zero the destination's so addObject mints one. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ComposeObject reused the destination's generation, so composing over an existing object on a versioning-enabled bucket archived the old copy and stored the new one under the same generation: a versioned listing showed two entries sharing an id, and the archived copy was no longer addressable on its own. Cloud Storage gives a compose result a new generation like any other write; zero the destination's so addObject mints one.