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

Enis Soztutar commented on HBASE-12972:
---------------------------------------

Not trying to cause a stir definitely just trying to reduce down the work. I am 
-1 for this for 1.0.x branch as it is against the compat guides. For 1.1, the 
motivation is for Phoenix to not have a branch for 0.98, a branch for 1.0 and a 
branch for 1.1. Phoenix already have coprocessors defined with HRegion as 
parameters and since the observers already come with HRegion parametsr, it is 
not a matter of depending on HRegion internals, but my understanding is that 
all of the coprocessors will break to compile. If Phoenix community wants 4.x 
releases supporting 0.98, 1.0 and 1.1, then it will be three branches rather 
than 2. Phoenix might as well decide to either only support 1.1, or have 3 
branches or not support 1.1 in 4.x releases. That is up for discussion in 
phoenix-dev I guess. Agreed that this is a Phoenix issue, but we are mainly 
doing this for Phoenix, so we should keep that into account. 

> 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.1.0
>
>         Attachments: HBASE-12972-0.98.patch, HBASE-12972.patch, 
> HBASE-12972.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 hooks.
> {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
(v6.3.4#6332)

Reply via email to