hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19235) CoprocessorEnvironment should be exposed to CPs
Date Mon, 13 Nov 2017 23:08:02 GMT

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

stack commented on HBASE-19235:
-------------------------------

[~chia7712] [~anoop.hbase]
bq. My sense is there is nothing that requires that a CP implement BaseEnironment and besides
it is IA.Private.

I misunderstood the suggestion above. BaseEnvironment is internal... yeah, could be good to
refer directly to it internally.

On [~appy] comment, we chatted offline. Appy is interested in the broader issue of IA labelling
and if we should allow it so super class can have different IA from subclass. Suggested we
take that up elsewhere, especially if we can turn up another example where a super IA.Private
when children are IA.LP or public would be convenient.

> 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)

Mime
View raw message