[
https://issues.apache.org/jira/browse/YARN-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832118#comment-13832118
]
Jarek Jarcec Cecho commented on YARN-1429:
------------------------------------------
Hi [~kkambatl],
thank you very much for reviewing my change! I guess that the order depends on
the use case. I felt that the {{YARN_CLASSPATH}} variable is meant for user to
plug-in their custom jars, that are not nor should be required by YARN itself.
My reasoning for putting such libraries at the end of the {{classpath}} was to
prohibit user to inject their own dependency before YARN's and possibly cause
random exceptions inside YARN code. For example by adding different
{{protobuf}}, {{guava}}, pick-your-favourite dependency that is usually
breaking binary compatibility between releases on the {{classpath}} prior the
expected version. However I didn't realized that this actually might be
desirable behavior in some cases. I'm not sure what should be the behavior
here, so I would appreciate guidance.
> YARN_CLASSPATH is referenced in yarn command comments but doesn't do anything
> -----------------------------------------------------------------------------
>
> Key: YARN-1429
> URL: https://issues.apache.org/jira/browse/YARN-1429
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
> Reporter: Sandy Ryza
> Priority: Trivial
> Labels: newbie
> Attachments: YARN-1429.patch
>
>
> YARN_CLASSPATH is referenced in the comments in
> ./hadoop-yarn-project/hadoop-yarn/bin/yarn and
> ./hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd, but doesn't do anything.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
