[
https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487675#comment-15487675
]
Heng Chen commented on HBASE-15921:
-----------------------------------
After unified, lots of callables could be removed. We could control retry in
AsyncProcess. The total logical should be clear.
As for AsyncProcess, it is complicated but also powerful, all replica logic,
traffic control, retry logic etc. has been implemented in it, and the AP has
been existed for all released versions, we could say it is stable. What we
need is to do some refactor for it. It is not a good idea to just abandon it.
Something i worried about with unification is performance, i will do it in
HBASE-16625
> Add first AsyncTable impl and create TableImpl based on it
> ----------------------------------------------------------
>
> Key: HBASE-15921
> URL: https://issues.apache.org/jira/browse/HBASE-15921
> Project: HBase
> Issue Type: Improvement
> Reporter: Jurriaan Mous
> Assignee: Jurriaan Mous
> Attachments: HBASE-15921.patch, HBASE-15921.v1.patch
>
>
> First we create an AsyncTable interface with implementation without the Scan
> functionality. Those will land in a separate patch since they need a refactor
> of existing scans.
> Also added is a new TableImpl to replace HTable. It uses the AsyncTableImpl
> internally and should be a bit faster because it does jump through less hoops
> to do ProtoBuf transportation. This way we can run all existing tests on the
> AsyncTableImpl to guarantee its quality.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
