[ https://issues.apache.org/jira/browse/HBASE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589420#comment-13589420 ]
Hadoop QA commented on HBASE-7928: ---------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12571388/HBASE-7928_trunk_2.patch against trunk revision . {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 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) 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 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/4601//console This message is automatically generated. > Scanning .META. with startRow and/or stopRow is not giving proper results > ------------------------------------------------------------------------- > > Key: HBASE-7928 > URL: https://issues.apache.org/jira/browse/HBASE-7928 > Project: HBase > Issue Type: Bug > Components: Usability > Affects Versions: 0.94.5 > Reporter: Jean-Marc Spaggiari > Assignee: ramkrishna.s.vasudevan > Attachments: HBASE-7928_0.94_1.patch, HBASE-7928_0.94_2.patch, > HBASE-7928_0.94_3.patch, HBASE-7928_0.94.patch, HBASE-7928_trunk_1.patch, > HBASE-7928_trunk_2.patch, HBASE-7928_trunk.patch > > > {code} > try { > HTable metaTable = new HTable(config, Bytes.toBytes(".META.")); > Scan scan = new Scan(); > scan.setStartRow(Bytes.toBytes("e")); > scan.setStopRow(Bytes.toBytes("z")); > ResultScanner scanner = metaTable.getScanner(scan); > Result[] results = scanner.next(100); > while (results.length > 0) { > for (Result result : results) { > System.out.println(Bytes.toString(result.getRow())); > } > results = scanner.next(100); > } > scanner.close(); > metaTable.close(); > } catch (Exception e) { > e.printStackTrace(); > } > {code} > This code will not return any result even if there is 10 tables with names > starting with "d" to "w", including one table called "entry". If you comment > the setStopRow you will get results, but will still get rows starting with > "d" even if setStartRow is set to "e". > Same code using with a user table is working fine. > Facing the same issue with the shell. > scan '.META.' , {STARTROW => 'e', LIMIT => 10} is returning rows starting by > "d". > scan '.META.' , {STARTROW => 'e', STOPROW => 'v', LIMIT => 10} is not > returning anything. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira