-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
batcheval: handle MVCC range tombstones in ClearRange
#80840
batcheval: handle MVCC range tombstones in ClearRange
#80840
Conversation
ab7e633
to
7f87857
Compare
cb77b2e
to
49aacac
Compare
7f87857
to
fe38145
Compare
49aacac
to
e5bd560
Compare
6607ed7
to
81fc002
Compare
81fc002
to
4178adb
Compare
4178adb
to
4b33df2
Compare
4b33df2
to
50aac2d
Compare
50aac2d
to
ac6424f
Compare
This one's ready for final review @aliher1911. |
This patch makes `ClearRange` account for MVCC range tombstones when updating MVCC stats. Release note: None
ac6424f
to
5ca916d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this PR not rebased so that ExperimentalPutMVCCRangeKey is still uses range key without value? I think it looks ok, but RangeValCount and RangeValBytes are missing.
No, I think it accounts for them: Reviewing an old clone again? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TFTR! bors r=aliher1911 |
Build succeeded: |
This patch makes
ClearRange
account for MVCC range tombstones whenupdating MVCC stats.
Touches #70412.
Release note: None