Add an override option for min-max range partitioning strategy for non-ctid sort key#3896
Closed
Add an override option for min-max range partitioning strategy for non-ctid sort key#3896
Conversation
jgao54
force-pushed
the
override-min-max
branch
2 times, most recently
from
ae2598f to
988b92d
Compare
jgao54
force-pushed
the
override-min-max
branch
from
988b92d to
b1f3ede
Compare
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.
When enabled, this allows override for MinMaxRangePartitioningStrategy instead of the default NTileBucketPartitioningStrategy.