[jira] [Commented] (HDFS-6418) Regression: DFS_NAMENODE_USER_NAME_KEY missing in trunk

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran commented on HDFS-6418:
--------------------------------------

How about
# {{DFSConfigKeys}} becomes the public keyset (for compatibility)
# a subclass of this, {{DFSPrivateConfigKeys}} becomes where private keys go
# We add the (deleted) tags but deprecate them.
# stuff in trunk that is new and private gets pushed into the private keys, promoted as and when its felt to make them public.

I can do the creation of the private keys file, revert the deleted keys -enough to help me build/link my code...leaving the choice of new stuff to keep private to others

> 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
>
> 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)