Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 14 Jul 2014 18:16:07 +0000 (UTC)
From: "Jesse Yates (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12726664.1405020068614.37281.1405361767756@arcas>
In-Reply-To: <JIRA.12726664.1405020068614@arcas>
References: <JIRA.12726664.1405020068614@arcas>
Subject: [jira] [Comment Edited] (HBASE-11497) Expose RpcScheduling
 implementations as LimitedPrivate interfaces
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jesse Yates edited comment on HBASE-11497 at 7/14/14 6:14 PM:
--------------------------------------------------------------

bq. so it's at your own risk to inherit from it

Fair enough. Not supporting .3 isn't a deal breaker for phoenix.

+1 on addendum


was (Author: jesse_yates):
bq. so it's at your own risk to inherit from it

Fair enough. Will need a slight rework our patch on the phoenix side, but not supporting .3 version isn't a big deal.

+1 on addendum

> Expose RpcScheduling implementations as LimitedPrivate interfaces
> -----------------------------------------------------------------
>
>                 Key: HBASE-11497
>                 URL: https://issues.apache.org/jira/browse/HBASE-11497
>             Project: HBase
>          Issue Type: Improvement
>          Components: io, regionserver, Usability
>    Affects Versions: 0.99.0, 0.98.4
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>             Fix For: 0.99.0, 0.98.4, 2.0.0
>
>         Attachments: HBASE-11497-0.98.patch, HBASE-11497.patch, abstract-rpc-sched.patch, hbase-11497-0.98-v0.patch
>
>
> In PHOENIX-938 we are attempting to resolve cross-RS deadlocks in indexing by adding custom RPC handlers (so regular puts/reads don't interfere with index updates). However, we've run into a couple of snags where the interfaces change, making it a bit more difficult to support interoperability between minor versions as the underlying RPC handling changed (for the better, but still different :).
> This would just mark those interfaces Public, Evolving, so we still have some flexibility, but don't break existing usage.
> Note, this kind of thing will come up for any client who is doing custom RPC handling - beyond the recently added flexibility - but wants to stay in line with the current HBase implementation (rather than building their own RPC handling mechanisms).


--
This message was sent by Atlassian JIRA
(v6.2#6252)