Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 22 Sep 2013 23:54:32 +0000 (UTC)
From: "Vandana Ayyalasomayajula (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12665605.1377554604964.646.1379894072140@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=13774177#comment-13774177 ] 

Vandana Ayyalasomayajula commented on HBASE-9343:
-------------------------------------------------

Hi,

I am on maternity leave till 9th December, 2013. If you need any assistance please contact olgan@yahoo-inc.com.

Thanks
Vandana

On Sep 18, 2013, at 11:49 AM, Francis Liu (JIRA) <jira@apache.org> wrote:

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

Francis Liu commented on HBASE-9343:
------------------------------------

[~ndimiduk] IMHO adding the new streaming scanner api to /<table>/scanner would convolute that resource. I think your original proposal of '<table>/*' (AKA suffix globing in the doc) is inline with existing apis and I'd be more amenable to that. It seems that the suffix globing api only has one query parameter so there shouldn't be any conflicts. Are we trying to avoid adding a new resource, is that the concern?

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.0, 0.96.1

       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


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

                
> 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.0, 0.96.1
>
>         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
>
>
> 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