You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2017/01/19 19:17:26 UTC
[jira] [Commented] (YARN-4985) Refactor the coprocessor code &
other definition classes into independent packages
[ https://issues.apache.org/jira/browse/YARN-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830428#comment-15830428 ]
Sangjin Lee commented on YARN-4985:
-----------------------------------
As part of this, it would also be good to see if it is feasible to get rid of the hbase-tests module and relocate the tests into the client and the server modules respectively. Once client and server are separated, the hbase-tests module becomes awkward.
Another part about the "server" module: since it should run in the hbase runtime, the pom should prescribe the hbase version and the appropriate hadoop version, rather than using the trunk hadoop version, for its dependencies. In other words, the pom for the server module should strongly resemble the current hbase-tests module.
The schema creator is an interesting case. I think a case can be made for it to be consider either "server" or "client". If it becomes too much work to locate it in the server module, I don't think it's a bad idea to keep it in the client module.
> 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: Vrushali C
> Labels: YARN-5355
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org