Tak-Lon (Stephen) Wu created HBASE-26714:
--------------------------------------------
Summary: 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
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)
