[
https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879210#comment-15879210
]
Sangjin Lee commented on YARN-4985:
-----------------------------------
I went over the coprocessor code in some detail, and largely confirmed what you
mentioned above. There are a number of classes that the coprocessor code
depends on that the hbase "client" code also depends on; e.g. FlowRunColumn.
The only code that can probably moved entirely into hbase-server is those
HBaseTimelineStorageUtils methods that are exercised by the coprocessor. The
only callers are the coprocessor in that case.
There might be a way to make maven create a combined jar file for the
coprocessor purposes, but I can't think of a straightforward way to do this.
It'd probably involve a pretty hacky way to pull that off, and I'm not sure if
the benefit justifies the work...
> Refactor the coprocessor code & other definition classes into independent
> packages
> ----------------------------------------------------------------------------------
>
> Key: YARN-4985
> URL: https://issues.apache.org/jira/browse/YARN-4985
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Vrushali C
> Assignee: Haibo Chen
> Labels: YARN-5355
> Attachments: YARN-4985-YARN-5355.poc.patch,
> YARN-4985-YARN-5355.prelim.patch
>
>
> As part of the coprocessor deployment, we have realized that it will be much
> cleaner to have the coprocessor code sit in a package which does not depend
> on hadoop-yarn-server classes. It only needs hbase and other util classes.
> These util classes and tag definition related classes can be refactored into
> their own independent "definition" class package so that making changes to
> coprocessor code, upgrading hbase, deploying hbase on a different hadoop
> version cluster etc all becomes operationally much easier and less error
> prone to having different library jars etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
