geode
geode copied to clipboard
GEODE-10453 - don't lookup old key in case of REMOVE_DUE_TO_GII_TOMBSTONE_CLEANUP and CompactRangeIndex
- GEODE-10453 - in case of REMOVE_DUE_TO_GII_TOMBSTONE_CLEANUP and CompactRangeIndex, specify not to lookup old key, which is very expensive operation. It's actually broken and regression. All the tombstone entries are going to be NullToken and cause class cast exception for every single remove compare if looking up old key. There is no old key during initial tombstone image sync up from lead peer.
For all changes:
-
[ GEODE-10453] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
-
[Yes ] Has your PR been rebased against the latest commit within the target branch (typically
develop)? -
[ Yes] Is your initial contribution a single, squashed commit?
-
[ Yes] Does
gradlew buildrun cleanly? -
[ No] Have you written or updated unit tests to verify your changes?
-
[ No] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?