[
https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15323369#comment-15323369
]
Jurriaan Mous commented on HBASE-15921:
---------------------------------------
The primary reason I made the new TableImpl because I wanted to run all
existing Tests on table to guarantee AyncTable is working correctly with all
exotic conditions being tested. It would be too much work to duplicate all
table test code and convert it to async. I wanted to also see how TableImpl
behaves in performance tests before deciding definite strategy. That's why
HTable is not yet removed in current latest patch. We could indeed introduce a
way to keep both in with a configuration and also test both while TableImpl
stabilizes.
> 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)
