[
https://issues.apache.org/jira/browse/HBASE-18954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194220#comment-16194220
]
Anoop Sam John commented on HBASE-18954:
----------------------------------------
On the confs added to new class CoprocessorConfigurations - U want to make this
class exposed to CPs (As the original one , the Host , is made private now)?
(The new class is missing the InterfaceAudience now)
But why we have to expose this? All these confs being used in the conf.xml file
by the user only right? I mean why a CP user has to know this constant ? For
dynamic loading of CPs, we have APIs right? So am not very sure why these
confs to be exposed as a Class level. Yes these are exposed but that is at the
conf xml file and all the config names are exposed ones.
> Make *CoprocessorHost classes private
> -------------------------------------
>
> Key: HBASE-18954
> URL: https://issues.apache.org/jira/browse/HBASE-18954
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Appy
> Assignee: Appy
> Labels: incompatible
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18954.master.001.patch
>
>
> Move out configuration name constants (into Coprocessor class?) and made Host
> classes private.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
