Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6371618FD8 for ; Wed, 17 Jun 2015 15:44:01 +0000 (UTC) Received: (qmail 91764 invoked by uid 500); 17 Jun 2015 15:44:01 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 91726 invoked by uid 500); 17 Jun 2015 15:44:01 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 91570 invoked by uid 99); 17 Jun 2015 15:44:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2015 15:44:01 +0000 Date: Wed, 17 Jun 2015 15:44:01 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13902) Remove Sync RpcClientImpl MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589942#comment-14589942 ] stack commented on HBASE-13902: ------------------------------- bq. Maybe the best way is to keep RpcClientImpl in at this moment, implement the async methods and remove it later if it proves to be slower with all the new code in. Lets get some numbers first. If it is NOT slower (or close enough) and it all works, lets try and go with the removal/simplification. > Remove Sync RpcClientImpl > ------------------------- > > Key: HBASE-13902 > URL: https://issues.apache.org/jira/browse/HBASE-13902 > Project: HBase > Issue Type: Improvement > Components: Client > Reporter: Jurriaan Mous > Assignee: Jurriaan Mous > Attachments: HBASE-13902.patch > > > For an async Table api to be supported we need to remove the sync RpcClientImpl. > For the Async Table Api some internals for scanning are changed to use async apis so they can't be used with the Sync RpcClientImpl. -- This message was sent by Atlassian JIRA (v6.3.4#6332)