[ https://issues.apache.org/jira/browse/HBASE-11990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136447#comment-14136447 ]
Hadoop QA commented on HBASE-11990: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12669218/HBASE-11990-20140916-v5.patch against trunk revision . ATTACHMENT ID: 12669218 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 3 new or modified tests. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2 warning messages. {color:red}-1 findbugs{color}. The patch appears to introduce 1 new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 site{color}. The mvn site goal succeeds with this patch. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.security.visibility.TestEnforcingScanLabelGenerator org.apache.hadoop.hbase.rest.TestScannersWithLabels org.apache.hadoop.hbase.security.access.TestScanEarlyTermination org.apache.hadoop.hbase.replication.TestPerTableCFReplication Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/10927//console This message is automatically generated. > Make setting the start and stop row for a specific prefix easier > ---------------------------------------------------------------- > > Key: HBASE-11990 > URL: https://issues.apache.org/jira/browse/HBASE-11990 > Project: HBase > Issue Type: New Feature > Components: Client > Reporter: Niels Basjes > Attachments: 11990v4.txt, HBASE-11990-20140916-v2.patch, > HBASE-11990-20140916-v3.patch, HBASE-11990-20140916-v5.patch, > HBASE-11990-20140916-v6.patch, HBASE-11990-20140916.patch > > > If you want to set a scan from your application to scan for a specific row > prefix this is actually quite hard. > As described in several places you can set the startRow to the prefix; yet > the stopRow should be set to the prefix '+1' > If the prefix 'ASCII' put into a byte[] then this is easy because you can > simply increment the last byte of the array. > But if your application uses real binary rowids you may run into the scenario > that your prefix is something like > {code}{ 0x12, 0x23, 0xFF, 0xFF }{code} Then the increment should be {code}{ > 0x12, 0x24 }{code} > I have prepared a proposed patch that makes setting these values correctly a > lot easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)