feat: support dynamic-bucket partial-update#317
Merged
JingsongLi merged 1 commit intoMay 14, 2026
Conversation
Signed-off-by: QuakeWang <wangfuzheng0814@foxmail.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
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.
Purpose
Linked issue: follow-up to #256
This PR adds basic
merge-engine=partial-updatesupport for primary-key tables usingbucket=-1dynamic bucket mode.It extends the existing fixed-bucket partial-update support to non-cross-partition dynamic bucket tables, including partitioned tables whose primary keys include partition fields. Cross-partition dynamic bucket partial-update remains unsupported and fails fast.
Brief change log
merge-engine=partial-updatefor non-cross-partitionbucket=-1PK tables.merge-engine=partial-updatewith cross-partition dynamic bucket explicitly unsupported.Tests
API and Format
This PR uses the existing dynamic bucket HASH index format and does not introduce a new storage format.
Documentation