[core] Support column placement policies for MAP shared-shredding#8743
Merged
Conversation
Contributor
|
+1 |
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
This is a subtask of MAP shared-shredding support.
This PR adds configurable physical column placement policies for MAP shared-shredding.
It introduces the per-field option:
Supported policies are:
plain: place fields according to the MAP entry order.sequential: place fields according to their dictionary IDs.lru: preserve recently used field-to-column assignments and evict the least recently used columns. This is the default.The shared allocator now owns common file-level metadata collection, while each policy provides its own row allocation strategy. The selected policy is propagated through
MapSharedShreddingWritePlanFactoryand applied byMapSharedShreddingRowConverter.Schema validation now rejects unknown placement policies. Existing physical-layout tests explicitly use
plain, while new tests cover all three policies.Tests
plain,sequential, andlru.paimon-commonandpaimon-coretest suites.git diff --checkpassed.