[
https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879030#comment-15879030
]
Haibo Chen commented on YARN-4985:
----------------------------------
bq. What is the implication of not doing this refactoring? Is the original
problem of being able to build Hadoop and HBase from source resolved without
this, or does it depend on this?
The problem of building Hadoop and HBase2.0 has been resolved in YARN-5667.
This is more of an effort to make HBase 2.0 & Hadoop 3 integration in cases of
HBase 2.0 changes. and improve code organization to explicate, in the form of
modules, the issue that we are dealing with two hadoop-common versions. I'd
agree with you that if there is too much work, given that the benefits are very
limited, we should not do the refactoring.
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
