[
https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877293#comment-15877293
]
Sangjin Lee commented on YARN-4985:
-----------------------------------
Thanks for the update [~haibochen].
bq. With this new module, we do still have the coprocessor installation issue.
I am totally speculating here. Is it possible to configure maven so that it
will combine hbase-schema and hbase-server into one jar, as a workaround?
It might be doable, but it may involve a fairly advance maven trick to pull
that off. I haven't thought about what it might take.
Going back to the original question, were you able to see if there is any way
we can limit the dependency coming from the coprocessor code? If that is
possible, that is the best case scenario.
> 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]
