Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 21 Sep 2016 02:13:20 +0000 (UTC)
From: "Heng Chen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12974125.1464675867000.622400.1474424000496@Atlassian.JIRA>
In-Reply-To: <JIRA.12974125.1464675867000@Atlassian.JIRA>
References: <JIRA.12974125.1464675867000@Atlassian.JIRA> <JIRA.12974125.1464675867359@arcas>
Subject: [jira] [Comment Edited] (HBASE-15921) Add first AsyncTable impl and
 create TableImpl based on it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 21 Sep 2016 02:13:22 -0000


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

Heng Chen edited comment on HBASE-15921 at 9/21/16 2:12 AM:
------------------------------------------------------------

The patch [~carp84] supplied missed some thing but i think it has been implemented in AP
1.  How to deal with batch?  For batch puts,  how to control traffic?
2.  How to deal with replica calls?
3.  How to deal with retry and different Exception handling?


And after you deal with these things,  It is just another AsyncProcess i think.


was (Author: chenheng):
The patch [~carp84] supplied missed some thing but i think it has been implemented in AP
1.  How to deal with batch?  For batch puts,  how to control traffic?
2.  How to deal with replica calls?
3.  How to deal with retry and different Exception handling?

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