[ 
https://issues.apache.org/jira/browse/HADOOP-9902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004152#comment-14004152
 ] 

Allen Wittenauer commented on HADOOP-9902:
------------------------------------------

YARN-1429 has (unintentionally) added a lot of complexity with questionable 
benefits likely due to the parties involved not realizing that the 
functionality they seek is already there.  In any case, with this change, we 
have this situation:

{code}
HADOOP_USER_CLASSPATH           =>   CLASSPATH:HADOOP_USER_CLASSPATH

YARN_USER_CLASSPATH             =>   CLASSPATH:YARN_USER_CLASSPATH

HADOOP_USER_CLASSPATH &         =>   
CLASSPATH:HADOOP_USER_CLASSPATH:YARN_USER_CLASSPATH
YARN_USER_CLASSSPATH

HADOOP_USER_CLASSPATH_FIRST     =>   
HADOOP_USER_CLASSPATH:CLASSPATH:YARN_USER_CLASSPATH

YARN_USER_CLASSPATH_FIRST       =>   
YARN_USER_CLASSPATH:CLASSPATH:HADOOP_USER_CLASSPATH

HADOOP_USER_CLASSPATH_FIRST &   =>   
YARN_USER_CLASSPATH:HADOOP_USER_CLASSPATH:CLASSPATH
YARN_USER_CLASSPATH_FIRST
{code}

In the case of the other YARN_xxx dupes, the new code causes an override for 
YARN apps.  In order to keep the consistency with the rest of the system, we 
should probably keep the same logic... essentially, YARN_USER_CLASSPATH will 
override HADOOP_USER_CLASSPATH entirely when running 'yarn xxx'. 

Ideally, we'd just back out YARN-1429 though and inform users of 
HADOOP_USER_CLASSPATH. 



> Shell script rewrite
> --------------------
>
>                 Key: HADOOP-9902
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9902
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 3.0.0, 2.1.1-beta
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>         Attachments: HADOOP-9902.txt, hadoop-9902-1.patch, more-info.txt
>
>
> Umbrella JIRA for shell script rewrite.  See more-info.txt for more details.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to