Implementing Bigtable TimestampRangeFilter. #1321
Merged
Conversation
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
Also implementing a separate TimestampRange class since it will need to be used to limit data requests to certain ranges (e.g. in ``Mutation.DeleteFromColumn.time_range`` in the Bigtable data `.proto` spec).
googlebot added the cla: yes 
Contributor Author
| @tseaver This is the final filter! After this, I'll implement the |
Contributor
| LGTM |
dhermes added a commit that referenced this pull request Dec 22, 2015
Implementing Bigtable TimestampRangeFilter.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
Also implementing a separate
TimestampRangeclass since it will need to be used to limit data requests to certain ranges (e.g. inMutation.DeleteFromColumn.time_rangein the Bigtabledata
.protospec).