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 "Jian He (JIRA)" <ji...@apache.org> on 2016/05/12 00:12:13 UTC
[jira] [Updated] (YARN-2506) TimelineClient should NOT be in
yarn-common project
[ https://issues.apache.org/jira/browse/YARN-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jian He updated YARN-2506:
--------------------------
Target Version/s: 3.0.0 (was: 2.8.0)
bq. Why not do this in trunk?
Having two diverged code base to maintain is not helpful. This is not a simple move, because of module cycle dependency.
bq. Seems like something useful as part of 3.x
sure keep it for 3.x then.
> TimelineClient should NOT be in yarn-common project
> ---------------------------------------------------
>
> Key: YARN-2506
> URL: https://issues.apache.org/jira/browse/YARN-2506
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Zhijie Shen
> Priority: Critical
>
> YARN-2298 incorrectly moved TimelineClient to yarn-common project. It doesn't belong there, we should move it back to yarn-client module.
--
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