[jira] Updated: (HBASE-1845) Discussion issue for multi calls, MultiDelete, MultiGet and MultiPut

["Erik Holstad (JIRA)" <ji...@apache.org>]

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

Erik Holstad updated HBASE-1845:
--------------------------------

    Attachment: multi-v1.patch

Added a first draft of something that is a way to deal with batching of all types of actions, Deletes, Gets and Puts.

The patch includes a couple of different classes to deal with sending and receiving theses multi calls. The calls to the different Region servers
are threaded on the client, but the instantiation is happening in the call at the moment, will be moved so we don't have to do it every time.
The return format from all the calls multi(List<Delete>), multi(List<Get>) and multi(List<Put>) all return the same type Result [] of the same length
as the request to the specific RS. For all elements where the Result[i] == null we have to retry the action, from the client. This common return type
adds a little bit of overhead for returns of Puts and Deletes but is needed to keep it simple and generic.

Changed the Row interface a little to be WritableComparable<Row>, needed for the new methods.

I have only done sanity check tests so far and are going to add more test to cover corner cases, but just wanted
to get the first draft out there to get feedback.

> Discussion issue for multi calls, MultiDelete, MultiGet and MultiPut
> --------------------------------------------------------------------
>
>                 Key: HBASE-1845
>                 URL: https://issues.apache.org/jira/browse/HBASE-1845
>             Project: Hadoop HBase
>          Issue Type: New Feature
>            Reporter: Erik Holstad
>             Fix For: 0.21.0
>
>         Attachments: multi-v1.patch
>
>
> I've started to create a general interface for doing these batch/multi calls and would like to get some input and thoughts about how we should handle this and what the protocol should
> look like. 
> First naive patch, coming soon.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.