hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12972) Region, a supportable public/evolving subset of HRegion
Date Thu, 26 Feb 2015 17:35:05 GMT

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

Andrew Purtell commented on HBASE-12972:

bq. Looks like the current patch makes changes that won't allow it in 1.0.z (non-binary compat
changes to existing LimitedPrivate.Evolving, adding new features to LimitedPrivate.Evolving).

Please point these changes out where you find them. 

bq. Can we aim for 0.98.y, 1.1.z, 2.y.z, or would folks prefer feedback to make it compat?

Well we should have a supportable 'Region' interface for Phoenix 1.0, which implies in HBase
1.0.x at least. Otherwise they are going to need to continue to work directly with HRegion
and SplitTransaction, and other things I would really like to -1 over there but can't if there
is no realistic alternative.

I did say this above:
'm treating introduction of the Region interface as a singularity of sorts for coprocessors:
neither source nor binary compatibility will be maintained. I don't see the harm in a singularity,
HRegion isn't supported, that's the point of this work... to replace it with something that
is. However, after there is a first workable patch if it's not too onerous to make addtional
changes that keep source or binary compatibility then we can do that. 

Let's discuss.

> Region, a supportable public/evolving subset of HRegion
> -------------------------------------------------------
>                 Key: HBASE-12972
>                 URL: https://issues.apache.org/jira/browse/HBASE-12972
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11
>         Attachments: HBASE-12972-0.98.patch, HBASE-12972-0.98.patch, HBASE-12972-0.98.patch
> On HBASE-12566, [~lhofhansl] proposed:
> {quote}
> Maybe we can have a {{Region}} interface that is to {{HRegion}} is what {{Store}} is
to {{HStore}}. Store marked with {{@InterfaceAudience.Private}} but used in some coprocessor
> {quote}
> By example, now coprocessors have to reach into HRegion in order to participate in row
and region locking protocols, this is one area where the functionality is legitimate for coprocessors
but not for users, so an in-between interface make sense.
> In addition we should promote {{Store}}'s interface audience to LimitedPrivate(COPROC).

This message was sent by Atlassian JIRA

View raw message