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

stack commented on HBASE-13784:
-------------------------------

bq. I am thinking of either making a clean Table implementation using 
AsyncTable internally or using the AsyncTable already within HTable itself.

Ok. Yes, it would be nice if you could slot in your AsyncTable everywhere to 
make sure it works in 'sync' mode blocking on the promise. Can you use junit 
parameterize (http://junit.org/apidocs/org/junit/runners/Parameterized.html) so 
tests run with current HTable implementation and then again with your Async'd 
HTable Implementation?

You could choose a few of the important client-side junits and have the work in 
the two modes?

Looking at TestFromClientSide, probably the biggest client-side set of tests, 
it still has a bunch of deprecated 'new HTable' usage. I could help by doing 
cleanup on this test so it all went via Connection to get Table instances..  
Would then have to jigger Connection and ConnectionFactory per parameterized 
run to return pure HTable for one run as it does now and then your fancy 
async'y version for the next run. 

If you make a list of junit test suites you'd like to parameterize and note 
obstacles to your getting your AsyncTable in under them, I can help with 
unblocking your obstacles.

Thanks [~jurmous]






> Add Async Client Table API
> --------------------------
>
>                 Key: HBASE-13784
>                 URL: https://issues.apache.org/jira/browse/HBASE-13784
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jurriaan Mous
>            Assignee: Jurriaan Mous
>         Attachments: HBASE-13784-v1.patch, HBASE-13784-v2.patch, 
> HBASE-13784-v3.patch, HBASE-13784-v4.patch, HBASE-13784.patch
>
>
> With the introduction of the Async HBase RPC Client it is possible to create 
> an Async Table API and more. This issue is focussed on creating a first async 
> Table API so it is possible to do any non deprecated Table call in an async 
> way.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to