[
https://issues.apache.org/jira/browse/TEZ-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394029#comment-14394029
]
Gopal V commented on TEZ-2270:
------------------------------
Filed as a place-holder until more analysis next week.
> TezClient.create() with AM localresources CLASSPATH order (Rolling Upgrade)
> ---------------------------------------------------------------------------
>
> Key: TEZ-2270
> URL: https://issues.apache.org/jira/browse/TEZ-2270
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Gopal V
> Labels: RollingUpgrade
>
> When a Tez AM is started with a LocalResource which is also present on the
> cluster, the added JAR should be preferred to the cluster version (during
> rolling upgrades).
> Running a different version on an existing cluster results shows
> incompatibilities triggered by the fact that the tez.tar.gz files are ahead
> of the cluster classpath, while the LocalResources are added after the
> cluster classpath.
> Mixing the order up results in the user-added JAR being ineffective in
> forcing the client version over the cluster version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
