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

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

I was misled by the current zh implementation in HBase...

The common way of using zookeeper is cache the data at client side and use 
watcher to update the cached data. So we do not need to implement a client that 
read data from zookeeper asynchronously. Instead, just use the NodeCache or 
TreeCache or whatever cache  in curator to keep the data in memory, and get the 
data directly, no Future needed. The cache will updated in background. This 
will greatly simplify the logic.

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
>            Reporter: Jurriaan Mous
>            Assignee: Jurriaan Mous
>         Attachments: 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