[TEZ-2168] Fix application dependencies on mutually exclusive artifacts: tez-yarn-timeline-history and tez-yarn-timeline-history-with-acls

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.6.1
• Target Version/s: 0.6.1
• Assignee: Hitesh Shah
• Reporter: Hitesh Shah
• Created: 02/Mar/15 22:44
• Updated: 30/Jun/15 04:53
• Resolved: 11/Mar/15 04:43

Description

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.

Issue Links

• relates to: PIG-4500 Pig's tez engine has issue when working with ATS