[
https://issues.apache.org/jira/browse/HDFS-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047685#comment-14047685
]
Hudson commented on HDFS-6418:
------------------------------
SUCCESS: Integrated in Hadoop-Hdfs-trunk #1790 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1790/])
HDFS-6418. Regression: DFS_NAMENODE_USER_NAME_KEY missing (stevel:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1606536)
* /hadoop/common/trunk
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
> Regression: DFS_NAMENODE_USER_NAME_KEY missing in trunk
> -------------------------------------------------------
>
> Key: HDFS-6418
> URL: https://issues.apache.org/jira/browse/HDFS-6418
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 3.0.0, 2.5.0
> Reporter: Steve Loughran
> Assignee: Tsz Wo Nicholas Sze
> Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: h6418_20140619.patch
>
>
> Code i have that compiles against HADOOP 2.4 doesn't build against trunk as
> someone took away {{DFSConfigKeys.DFS_NAMENODE_USER_NAME_KEY}} -apparently in
> HDFS-6181.
> I know the name was obsolete, but anyone who has compiled code using that
> reference -rather than cutting and pasting in the string- is going to find
> their code doesn't work.
> More subtly: that will lead to a link exception trying to run that code on a
> 2.5+ cluster.
> This is a regression: the old names need to go back in, even if they refer to
> the new names and are marked as deprecated
--
This message was sent by Atlassian JIRA
(v6.2#6252)
