Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 6 Sep 2013 23:49:53 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12665605.1377554604964.95227.1378511393035@arcas>
In-Reply-To: <JIRA.12665605.1377554604964@arcas>
References: <JIRA.12665605.1377554604964@arcas>
Subject: [jira] [Commented] (HBASE-9343) Implement stateless scanner for
 Stargate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760759#comment-13760759 ] 

Nick Dimiduk commented on HBASE-9343:
-------------------------------------

Please verify your changes vs. Hadoop2 profile:

{noformat}
$ mvn -Dhadoop.profile=2.0 clean compile
...
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project hbase-hadoop2-compat: Compilation failure
[ERROR] /Users/ndimiduk/repos/hbase/hbase-hadoop2-compat/src/main/java/org/apache/hadoop/hbase/rest/MetricsRESTSourceImpl.java:[30,7] org.apache.hadoop.hbase.rest.MetricsRESTSourceImpl is not abstract and does not override abstract method incrementFailedScanRequests(int) in org.apache.hadoop.hbase.rest.MetricsRESTSource
{noformat}
                
> 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
>         Attachments: HBASE-9343_94.00.patch, HBASE-9343_94.01.patch, HBASE-9343_trunk.00.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 &lt; N ), then M rows will be returned to the user.
> 5. If start row, end row and limit (say N ) are specified and N &lt; number of rows between start row and end row, then N rows from start row
> will be returned to the user. If N &gt; (number of rows between start row and end row (say M), then M number of rows will be returned to the
> user.

--
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