hbase-issues mailing list archives

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

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

Appy commented on HBASE-19235:
------------------------------

Seems to be turning into bikeshed. I am fine with latest v3 mainly because I think it's probably
better to have bad code internally than have users deal with the confusion (if those are the
only two options).

> 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, HBASE-19235_V3.patch, HBASE-19235_V3.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