[
https://issues.apache.org/jira/browse/HBASE-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392252#comment-14392252
]
Hudson commented on HBASE-12972:
--------------------------------
SUCCESS: Integrated in HBase-1.1 #349 (See
[https://builds.apache.org/job/HBase-1.1/349/])
HBASE-13384 Fix Javadoc warnings introduced by HBASE-12972 (apurtell: rev
b75a4c8ef01e0e68e4f7b1e1f43884ef38ccacad)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Region.java
> 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-branch-1.patch,
> HBASE-12972.patch, HBASE-12972.patch, HBASE-12972.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)
