You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/02/05 03:07:00 UTC

[jira] [Commented] (HBASE-26714) Introduce path configuration for system coprocessors

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

Hudson commented on HBASE-26714:
--------------------------------

Results for branch branch-2.4
	[build #282 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/282/]: (/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/282/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/282/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/282/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/282/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Introduce path configuration for system coprocessors
> ----------------------------------------------------
>
>                 Key: HBASE-26714
>                 URL: https://issues.apache.org/jira/browse/HBASE-26714
>             Project: HBase
>          Issue Type: Task
>          Components: Coprocessors
>    Affects Versions: 2.5.0, 3.0.0-alpha-3
>            Reporter: Tak-Lon (Stephen) Wu
>            Assignee: Tak-Lon (Stephen) Wu
>            Priority: Major
>             Fix For: 3.0.0-alpha-3
>
>
> Currently when region server starts, system coprocessors are normally loaded as part of the local classpath and the jar is stored in the local storage; in short words, Operator would have to copy the jar to each host (or a shared file system) and construct it as part of HBASE_CLASSPATH. 
> although operator may have been doing the presetup of copying jar and making it available to the HBASE_CLASSPATH without any issue, it could be helpful if we provide an alternative method and centralize this configuration in hbase-site similar to the support of table-level coprocessor, e.g. configuring {{hbase.coprocessor.region.classes}} with the local/remote path along with the classname with a specific path token in the form of {{className|priority|path}}.
> Similarly in HBASE-23710, it provided the priority configuration via hbase-site that this new improvement aligns with the same purpose, and further help to simplify the deployment of System Coprocessors to e.g. hdfs or supported cloud storage.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)