Repro REST vs non-REST concurrent replace behaviour#15914
Draft
smaheshwar-pltr wants to merge 1 commit intoapache:mainfrom
Draft
Repro REST vs non-REST concurrent replace behaviour#15914smaheshwar-pltr wants to merge 1 commit intoapache:mainfrom
smaheshwar-pltr wants to merge 1 commit intoapache:mainfrom
Conversation
…and non-REST Adds a CatalogTests test that starts a replace transaction, concurrently adds a property, then commits the replace. The concurrent property should survive since the replace did not remove it. Passes on REST (SetProperties delta merged server-side), fails on non-REST catalogs (stale TableMetadata committed directly, overwriting concurrent changes). Co-Authored-By: Claude Opus 4.6 (1M context) <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.
No description provided.