Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 24 Mar 2011 23:08:05 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2062469374.10059.1301008085813.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2009650153.1540.1297904484592.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-3541) REST Multi Gets
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-3541:
-------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Applied to TRUNK.  Thanks for the patch Elliott!

> REST Multi Gets
> ---------------
>
>                 Key: HBASE-3541
>                 URL: https://issues.apache.org/jira/browse/HBASE-3541
>             Project: HBase
>          Issue Type: Improvement
>          Components: rest
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>            Priority: Minor
>             Fix For: 0.92.0
>
>         Attachments: HBASE-3541_1.patch, HBASE-3541_3.patch, HBASE-3541_5.patch, multi_get_0.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Users currently using the REST interface do not have a way to ask for multiple rows within one http call.
> For my use case I want to get a set of rows that I know the key before hand.  It's a very small percentage of my table and may not be contiguous so the scanner is not the right use-case for me.  Currently the http overhead is the largest percentage of my processing time.
> Ideally I'd like to create a patch that would act very similar to:
> GET /table/?row[]="rowkey"&row[]="rowkey_two"
> HTTP/1.1 200 OK
> { 
>    "Rows":[ << Array of results equivalent to a single get >>]
> }
> This should be pretty backward compatible.  As it's just making the row key into a query string.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira