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

Anoop Sam John commented on HBASE-24421:
----------------------------------------

You mean a config which takes the jar path alone? That wont work because there 
can be more than one CP and can be from different paths.  Or else a totally new 
config for say master side cp which takes the form <jar path>|<class 
name>|priority.    Then why can't we do that in existing config itself? Too 
many configs will be confusing too.

> Support loading cluster level CPs from Hadoop file system
> ---------------------------------------------------------
>
>                 Key: HBASE-24421
>                 URL: https://issues.apache.org/jira/browse/HBASE-24421
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>            Priority: Major
>             Fix For: 3.0.0-alpha-1
>
>
> Right now we allow configuring CPs, which needs to be loaded from hadoop FS, 
> at table level. (Via the Java API or shell)
> > alter 't1', METHOD => 'table_att', 
> > 'coprocessor'=>'hdfs:///foo.jar|com.foo.FooRegionObserver|1001|arg1=1,arg2=2'
> But for the cluster level CPs at Master/RS/WAL level, only way is to config 
> at hbase-site.xml. But here we dont allow to specify any jar path. This jira 
> suggest to add such a feature
> Note: We already support config the priority of CP at xml level 
> (FQCN|<priority>).  Same way how shell command works we can take the jar 
> pathalso. <jar path>|<class name>|<priority>
> If no '|' separator at all, consider that as FQCN in the classpath. If one 
> '|' that will be FQCN and priority (Same as of today). If 2 '|' separators we 
> consider the 1st part as path to the external jar.
> This will help in cloud scenario specially with auto scaling. Or else 
> customer should be executing some special scripts to make the CP jar 
> available within the HBase classpath.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to