release-20.2: storageccl: tolerate rewriting span keys ending in interleaved sentinel #58259
Conversation
This file contains 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
Some index span keys have been observed to end with the interleaved sentinel value. It is not yet clear how these types of keys are created but from the perspective of the key-rewriter it has rewritten the key. Release note (sql change): Fix a bug in RESTORE where some unusual range boundaries in interleaved tables caused an error.
|
This change is |
dt
approved these changes
Dec 23, 2020
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.
Backport 1/1 commits from #58219.
/cc @cockroachdb/release
Some index span keys have been observed to end with the interleaved
sentinel value. It is not yet clear how these types of keys are created
but from the perspective of the key-rewriter it has rewritten the key.
Fixes #58080.
Release note (sql change): Fix a bug in RESTORE where some unusual range
boundaries in interleaved tables caused an error.