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
MOD-6597: Fix numeric index deletion #4513
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4513 +/- ##
==========================================
+ Coverage 85.43% 85.46% +0.03%
==========================================
Files 188 188
Lines 32892 32892
==========================================
+ Hits 28101 28111 +10
+ Misses 4791 4781 -10 ☔ View full report in Codecov by Sentry. |
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.
👍🏼 👏🏼
Successfully created backport PR for |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 2.6
git worktree add -d .worktree/backport-4513-to-2.6 origin/2.6
cd .worktree/backport-4513-to-2.6
git switch --create backport-4513-to-2.6
git cherry-pick -x 6e3bc74d48e3b56284e053c4e6670555d03dba9d 3925390ccd7625d3ce137d7f1048c7d922c0175c 87b3c1c184258f671d871b5a0eb64815b1136247 |
Successfully created backport PR for |
* Fix numeric index deletion bug * Remove periodic runs of the GC in test * Enhance test
Describe the changes in the pull request
We have a bug in our numeric index - we don't update the
revisionId
when we trim the Tree (inNumericRangeTree_TrimEmptyLeaves
), causing us not to abort the reading of the numeric index for an invalidated cursor upon opening an invalidatedNumericRangeIterator
, and possibly crash.Mark if applicable