[
https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15573685#comment-15573685
]
Duo Zhang commented on HBASE-15921:
-----------------------------------
{quote}
Is there any overlap in the test failures? There does not seem to be.
{quote}
I haven't change any existing logic in this patch. The timed out UTs are always
timed out in pre-commit...
{quote}
How does the client use zookeeper in async now Duo Zhang? We do not use a
watcher but we keep connection open to zk?
{quote}
Keep a connection to zk. Let's open another issue to discuss the zk part. I
think we could implement the client side zk related logic alone as it is much
simpler than the server side.
Let me write a release note.
> 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
> Affects Versions: 2.0.0
> Reporter: Jurriaan Mous
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-15921-v2.patch, HBASE-15921-v3.patch,
> HBASE-15921-v4.patch, HBASE-15921-v5.patch, HBASE-15921-v6.patch,
> HBASE-15921-v7.patch, HBASE-15921-v8.patch, HBASE-15921-v9.patch,
> HBASE-15921.demo.patch, 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)
