[
https://issues.apache.org/jira/browse/HBASE-19235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16250335#comment-16250335
]
stack commented on HBASE-19235:
-------------------------------
bq. It seems all CPEnvs extend the BaseEnvironment. What about using the
BaseEnvironment directly in private scope? Make the CoprocessorEnvironment be a
cp-only interface.
[~anoop.hbase] See the [~chia7712] comment above.
My sense is there is nothing that requires that a CP implement BaseEnironment
and besides it is IA.Private.
I'd be +1 on the patch (fix checkstyle on commit).
> CoprocessorEnvironment should be exposed to CPs
> -----------------------------------------------
>
> Key: HBASE-19235
> URL: https://issues.apache.org/jira/browse/HBASE-19235
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Affects Versions: 2.0.0-alpha-4
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Priority: Minor
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19235.patch, HBASE-19235_V2.patch
>
>
> Its sub interfaces are exposed with
> LimitedPrivate(HBaseInterfaceAudience.COPROC). So ideally all the functions
> in this are. Better we mark CoprocessorEnvironment also as CP exposed to
> avoid confusion.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
