fixed bugs in table.scan with 'limit' and row keys that cannot be UTF-8 encoded#4
Open
osboo wants to merge 7 commits intoeliangcs:masterfrom
Open
fixed bugs in table.scan with 'limit' and row keys that cannot be UTF-8 encoded#4osboo wants to merge 7 commits intoeliangcs:masterfrom
osboo wants to merge 7 commits intoeliangcs:masterfrom
Conversation
Author
|
hi @eliangcs! |
rows in scan are filtered using columns argument
added the possibility for removal non-existing column
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
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.
Hi, could you please consider merging this into master:
table.scannow works correctly (bug with sign fixed)row_prefixflag now can be arbitrary binary string which is the case for MD5 generated row keys. These keys cannot be UTF-8 encoded which made testing such database usage impossible. To fix this latest functionality from happybase was taken.