-
Notifications
You must be signed in to change notification settings - Fork 198
mongo: partition snapshots for numeric and string _id collections #4487
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
f45c14e
mongo: partition snapshots for numeric and string _id collections
andreyzhelnin-st 925889b
mongo: address PR review comments on _id partitioning
andreyzhelnin-st 8dac193
mongo: reduce e2e test doc count to 100 for faster local runs
andreyzhelnin-st b89e2fc
mongo: address PR review comments (round 2)
andreyzhelnin-st c21475e
fix(lint): restore stdlib import group separator in qrep_partition.go
andreyzhelnin-st 1a11c54
Merge remote-tracking branch 'origin/main' into mongo-id-partitioning
ilidemi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
for mongo, using inclusive-inclusive int range [start, end] is prone to missing data in the rare scenario where user has doubles mixed in with integers. For example, if the
_ids are 1, 2, 2.5, 3, 4; min/max will show up as 1 and 4, ended up with ranges [1, 2], [3, 4], we'd miss the 2.5 document.we could introduce a
NumericPartitionRangeand use inclusive-exclusive [start, end), similar toStringPartitionRange, to avoid any gaps.(While Mongo sorts by type so we don't have to worry about this for ObjectIDs, all numeric types are in the same type bucket)