[
https://issues.apache.org/jira/browse/HDFS-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988269#comment-13988269
]
Aaron T. Myers commented on HDFS-6056:
--------------------------------------
bq. Since nfs is in another project, do we still want to move all the
configuration keys to hadoop-common and hdfs? Maybe in this jira we can first
make the conf names more consistent and unified, and consider the moving part
in a separate jira?
Higher level question here - why is any of this code in Common? It's all to
support HDFS NFS access, so I don't really see how this could be used by
YARN/MR, or independently of HDFS. Given that, my suggestion would be to move
all the NFS-related code into the hadoop-hdfs-nfs project, and put all the
relevant configs there.
Having several of the configs in Common (and therefore with different prefixes
than the rest of the configs) only seems like it will cause user confusion, and
not really serve to help anything, given the above.
> Clean up NFS config settings
> ----------------------------
>
> Key: HDFS-6056
> URL: https://issues.apache.org/jira/browse/HDFS-6056
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: nfs
> Affects Versions: 2.3.0
> Reporter: Aaron T. Myers
> Assignee: Brandon Li
> Attachments: HDFS-6056.001.patch, HDFS-6056.002.patch
>
>
> As discussed on HDFS-6050, there's a few opportunities to improve the config
> settings related to NFS. This JIRA is to implement those changes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
