[
https://issues.apache.org/jira/browse/HBASE-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-2390.
-----------------------------------
Resolution: Fixed
Assignee: (was: Andrew Purtell)
This issue is specific to HBASE-2387 and stale. Resolving as 'Later'.
> [stargate] streaming scanners and multigets
> -------------------------------------------
>
> Key: HBASE-2390
> URL: https://issues.apache.org/jira/browse/HBASE-2390
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
>
> The Stargate data model supports packaging up a bunch of rows for a multi-put
> and for returning multiple rows out of a scanner in batch. The data model
> supports multi-get also but this is not currently implemented -- gets are
> driven by HTTP transactions requesting path specified resources, with widest
> scope being the row, as is the REST way. This issue is about how to maintain
> RESTful sematics on the one hand but also support multi-put _and_ multi-get;
> furthermore, to return results from multi-get and scanners in a streaming
> manner. Investigate Jersey multipart support. Can it support streaming the
> equivalent of List<RowResult>? Would it do the right thing given a list of
> models to marshal and send along?
> Acccording to this --
> http://n2.nabble.com/Hello-World-and-Welcome-to-jersey-multipart-td1343189.html
> -- the situation looks promising:
> {quote}
> The need for cleanup() is because the implementation knows how to buffer
> "large" body parts to temporary files on disk, so you don't blow away your
> JVM heap on a multi-gigabyte upload or download.
> {quote}
> I would prefer an API that does pure streaming, not store and forward, but
> that might be good enough.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
