Support multiple tables in BatchWrite and BatchGet #226
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
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.
This PR adds some new methods to BatchWrite and BatchGet that let them target multiple tables.
The API is a little bit ugly to keep backwards compatibility.
New stuff:
(*BatchWrite).PutInfor putting items in other tables(*BatchWrite).DeleteInand(*BatchWrite).DeleteInRangefor deleting items in other tables(*BatchGet).Fromand(*BatchGet).FromRangefor getting items from other tables(*BatchGet).ProjectTablefor specifying table-specific projections(*BatchGet).IterWithTablefor creating an iterator that keeps track of which table each item comes fromTODO
Mentioned in #113 as one of the features I want to change in v2 (or maybe v3 at this rate, I'll port this to the v2 branch soon).