Correct multi-column key partition ordering #61
Merged
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
To quote from the documentation: > With RANGE COLUMNS, a row matches a partition if all row values are less > than specified values. The first partition that matches row values will be > used. Previously, with `RANGE COLUMNS`, partition-manager got this logic backward, which led to partitions being considered "unfilled" and candidates for rename which actually had data in them. Fixes #60
ezekiel
approved these changes
Apr 12, 2023
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.
To quote from the documentation:
Previously, with
RANGE COLUMNS, partition-manager got this logic backward, which led to partitions being considered "unfilled" and candidates for rename which actually had data in them.Fixes #60