Return-Path: 
 <issues-return-131940-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1F295101E0
	for <apmail-hbase-issues-archive@www.apache.org>;
 Wed, 15 Jan 2014 20:41:27 +0000 (UTC)
Received: (qmail 79697 invoked by uid 500); 15 Jan 2014 20:41:22 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 79609 invoked by uid 500); 15 Jan 2014 20:41:22 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 79593 invoked by uid 99); 15 Jan 2014 20:41:21 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Jan 2014 20:41:21 +0000
Date: Wed, 15 Jan 2014 20:41:21 +0000 (UTC)
From: "Vandana Ayyalasomayajula (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12665605.1377554604964.10320.1389818481546@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
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

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

I have attached a new patch that maintains compatability with older APIs:
{quote}
GET /<table>/<rowkey> => existing behavior 
GET /<table>/<optional_prefix>*/<columns>/ => existing behavior
GET /<table>/<optional_prefix>* => new streaming scanner with prefix filter.
GET /<table>/<optional_prefix>*?<scan_args...> => new streaming scanner with prefix filter and scan parameters.
GET /<table>/* => new streaming scanner
GET /<table>/*?<scan_args...> => new streaming scanner with scan parameters
{quote}




> 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 &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 was sent by Atlassian JIRA
(v6.1.5#6160)