[ https://issues.apache.org/jira/browse/HBASE-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13872668#comment-13872668 ]
Hadoop QA commented on HBASE-9343: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12623219/HBASE-9343_trunk.05.patch against trunk revision . ATTACHMENT ID: 12623219 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 16 new or modified tests. {color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop 1.0 profile. {color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop 1.1 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:red}-1 site{color}. The patch appears to cause mvn site goal to fail. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8438//console This message is automatically generated. > Implement stateless scanner for Stargate > ---------------------------------------- > > Key: HBASE-9343 > URL: https://issues.apache.org/jira/browse/HBASE-9343 > Project: HBase > Issue Type: Improvement > Components: REST > Affects Versions: 0.94.11 > Reporter: Vandana Ayyalasomayajula > Assignee: Vandana Ayyalasomayajula > Priority: Minor > Fix For: 0.98.1, 0.99.0 > > Attachments: HBASE-9343_94.00.patch, HBASE-9343_94.01.patch, > HBASE-9343_trunk.00.patch, HBASE-9343_trunk.01.patch, > HBASE-9343_trunk.01.patch, HBASE-9343_trunk.02.patch, > HBASE-9343_trunk.03.patch, HBASE-9343_trunk.04.patch, > HBASE-9343_trunk.05.patch > > > The current scanner implementation for scanner stores state and hence not > very suitable for REST server failure scenarios. The current JIRA proposes to > implement a stateless scanner. In the first version of the patch, a new > resource class "ScanResource" has been added and all the scan parameters will > be specified as query params. > The following are the scan parameters > startrow - The start row for the scan. > endrow - The end row for the scan. > columns - The columns to scan. > starttime, endtime - To only retrieve columns within a specific range of > version timestamps,both start and end time must be specified. > maxversions - To limit the number of versions of each column to be returned. > batchsize - To limit the maximum number of values returned for each call to > next(). > limit - The number of rows to return in the scan operation. > More on start row, end row and limit parameters. > 1. If start row, end row and limit not specified, then the whole table will > be scanned. > 2. If start row and limit (say N) is specified, then the scan operation will > return N rows from the start row specified. > 3. If only limit parameter is specified, then the scan operation will return > N rows from the start of the table. > 4. If limit and end row are specified, then the scan operation will return N > rows from start of table till the end row. If the end row is > reached before N rows ( say M and M < N ), then M rows will be returned to > the user. > 5. If start row, end row and limit (say N ) are specified and N < number > of rows between start row and end row, then N rows from start row > will be returned to the user. If N > (number of rows between start row and > end row (say M), then M number of rows will be returned to the > user. -- This message was sent by Atlassian JIRA (v6.1.5#6160)