[kv] Treat full-schema partial writes as full row for DefaultRowMerger#3325
Open
zuston wants to merge 2 commits into
Open
[kv] Treat full-schema partial writes as full row for DefaultRowMerger#3325zuston wants to merge 2 commits into
zuston wants to merge 2 commits into
Conversation
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.
Purpose
Linked issue: close #xxx
Upper-layer frameworks sometimes route every upsert through
UpsertWriterpartial-update APIs even when all columns are provided. That forced thePartialUpdateRowMergerpath and prevented WAL optimizations that depend on DefaultRowMerger, producing excessive RocksDB gets and slowing tablet RPC.When targetColumns covers every index of the latest schema, behave like null target columns and keep plain DefaultRowMerger semantics.
Brief change log
Tests
API and Format
Documentation