[ 
https://issues.apache.org/jira/browse/HBASE-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15570206#comment-15570206
 ] 

Duo Zhang commented on HBASE-15921:
-----------------------------------

Ah I have removed the watcher related code in the new patch as we do not need 
it right now. And if we want to do async access to zk then curator is much 
simpler than our zk stuff as client only need to read a small set of data on 
zk. Now the client depend on Zookeeperwatcher, MasterAddressTrack, and maybe 
MetaTableAccessor. And for every class we only use  a very small part, it is a 
pain to modify such big classes...

And for now as we do not use async nor watcher, I can remove the curator 
dependency. We can continue this discussion in a new jira.

Thanks.

> 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.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)

Reply via email to