Detect and partition sparse region of UIDs #224
Merged
Conversation
This file contains 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
EnricoMi
force-pushed
the
partition-sparse-uid-range
branch
2 times, most recently
from
dbdbb63
to
0a81722
Compare
EnricoMi
force-pushed
the
partition-sparse-uid-range
branch
from
0a81722
to
63519a9
Compare
EnricoMi
force-pushed
the
partition-sparse-uid-range
branch
from
e70e97b
to
816fd32
Compare
EnricoMi
force-pushed
the
partition-sparse-uid-range
branch
from
80cf439
to
1bfb1b3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Loading data with Dgraph live loader will spread uids across the entire 64-bit unsigned value range. This renders uid partitioning useless.
This fix scans the value range for a sparse region following a dense region at the beginning of the uid range.