You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2015/03/03 23:40:05 UTC
[jira] [Updated] (TEZ-2168) Fix application dependencies on
mutually exclusive artifacts: tez-yarn-timeline-history and
tez-yarn-timeline-history-with-acls
[ https://issues.apache.org/jira/browse/TEZ-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hitesh Shah updated TEZ-2168:
-----------------------------
Target Version/s: 0.6.1
> Fix application dependencies on mutually exclusive artifacts: tez-yarn-timeline-history and tez-yarn-timeline-history-with-acls
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEZ-2168
> URL: https://issues.apache.org/jira/browse/TEZ-2168
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Hitesh Shah
> Attachments: TEZ-2168.1.post-script.patch, TEZ-2168.file-move.sh
>
>
> Feedback from Chris Wensel on dev list related to simplifying the build file for an app dependent on Tez.
> Currently, based on hadoop versions, one needs to choose between mutually exclusive artifacts: tez-yarn-timeline-history and tez-yarn-timeline-history-with-acls.
> Suggested options:
> create a single artifact tez-yarn-timeline-history compiled with a default dep of hadoop 2.6, that includes the Manager. update the TezClient code to gracefully fail if the Manager is not applicable (the runtime env is Hadoop 2.4).
> or
> offer tez-yarn-timeline-history-with-acls as an optional artifact for Hadoop 2.6 deployments, with the single Manager class in it, which in turn requires the tez-yarn-timeline-history artifact -- which is sufficient for a 2.4 runtime. if the user provides the additional -with-acls artifact, they are knowingly going to have problems on Hadoop 2.4.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)