Reorganized all local keys into two sections/range: by ID & by Key. #264
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.
This groups all of the range-local data contiguously into two sections,
making range traversals require less seeks and more importantly, less
maintenance as new range-local data is added going forward.
The trickiest part of this was upgrading the C++ code to properly
account for encoded keys, since it now has to decode the key and skip
the range ID or range Key to determine whether the tuple being compacted
is a transaction record or response cache entry.