Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add a method to get boundary primary keys #439

Closed
nblintao opened this issue Mar 11, 2019 · 1 comment
Closed

Add a method to get boundary primary keys #439

nblintao opened this issue Mar 11, 2019 · 1 comment
Assignees
@nblintao

Comments

@nblintao
Copy link
Contributor

Boundaries are a list of key ranges maintained by each FDB server. This information can be useful for splitting a large task (e.g. rebuild index for a large record store) into small tasks (e.g. rebuild index for records in certain primary key ranges) more evenly so that they can be executed in a parallel fashion efficiently.
@nblintao nblintao self-assigned this Mar 11, 2019
nblintao added a commit to nblintao/fdb-record-layer that referenced this issue Mar 11, 2019
@nblintao
Resolves FoundationDB#439: Add a method to get boundary primary keys
554dde5 
- Change name to getPrimaryKeyBoundariesAsync and put it on FDBRecordStore
- Change the interface from TupleRange to two tuple enpoints.
- Fix a bug of not packing the key with record subspace
- Fix a bug for primary keys with multiple fields
- Change hasSplitSuffix to hasSplitRecordSuffix
- Improve docs and release notes
@scgray scgray closed this as completed in 9833867 Mar 13, 2019
scgray added a commit that referenced this issue Mar 13, 2019
@scgray
Merge pull request #440 from nblintao/get-boundary-primary-keys
81ace5a 
Resolves #439: Add a method to get boundary primary keys
@nblintao
Copy link
Contributor Author

Resolved by #440

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nblintao nblintao

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nblintao