[
https://issues.apache.org/jira/browse/HBASE-16593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Heng Chen updated HBASE-16593:
------------------------------
Description:
Currently, HTable has two ways to deal with request, one is call RPC directly,
it is used to processed single action request such as Get, Delete, Append,
Increment. Another one is through AP to deal with multi action requests, such
as batch, mutation etc.
This issue is to unify them with AP only. It has some benefits, for example we
could implements async interface easily with AP, and we could make the client
logic more clear just use AP to communicate with Server.
HBASE-14703 has done some work (unify mutate and checkAndMutate with AP)
was:
Currently, HTable has two ways to deal with request, one is call RPC directly,
it is used to processed single action request such as Get, Delete, Append,
Increment. Another one is through AP to deal with multi action requests, such
as batch, mutation etc.
This issue is to unify them with AP only. It has some benefits, for example we
could implements async interface easily with AP, and we could make the client
logic more clear just use AP to communicate with Server.
> Unify HTable with AP
> --------------------
>
> Key: HBASE-16593
> URL: https://issues.apache.org/jira/browse/HBASE-16593
> Project: HBase
> Issue Type: Umbrella
> Reporter: Heng Chen
> Assignee: Heng Chen
>
> Currently, HTable has two ways to deal with request, one is call RPC
> directly, it is used to processed single action request such as Get, Delete,
> Append, Increment. Another one is through AP to deal with multi action
> requests, such as batch, mutation etc.
> This issue is to unify them with AP only. It has some benefits, for example
> we could implements async interface easily with AP, and we could make the
> client logic more clear just use AP to communicate with Server.
> HBASE-14703 has done some work (unify mutate and checkAndMutate with AP)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
