[
https://issues.apache.org/jira/browse/HADOOP-11022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137092#comment-14137092
]
Hudson commented on HADOOP-11022:
---------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #683 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/683/])
HADOOP-11022. User replaced functions get lost 2-3 levels deep (e.g., sbin)
(aw) (aw: rev 7971c97ec18f4fc6504f6a87d9ad02a1f5f01eea)
* hadoop-hdfs-project/hadoop-hdfs/src/main/bin/hdfs-config.sh
* hadoop-common-project/hadoop-common/src/main/bin/hadoop-config.sh
* hadoop-common-project/hadoop-common/src/main/bin/hadoop-functions.sh
* hadoop-yarn-project/hadoop-yarn/bin/yarn-config.sh
*
hadoop-common-project/hadoop-common/src/main/conf/hadoop-user-functions.sh.example
* hadoop-common-project/hadoop-common/src/main/conf/hadoop-env.sh
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-mapreduce-project/bin/mapred-config.sh
> User replaced functions get lost 2-3 levels deep (e.g., sbin)
> -------------------------------------------------------------
>
> Key: HADOOP-11022
> URL: https://issues.apache.org/jira/browse/HADOOP-11022
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.0.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HADOOP-11022.patch
>
>
> The code that protects hadoop-env.sh from being re-executed is also causing
> functions that the user replaced to get overridden with the defaults. This
> typically happens when running commands that nest, such as most of the
> content in sbin. Just running stuff out of bin (e.g., bin/hdfs --daemon
> start namenode) does not trigger this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
