[
https://issues.apache.org/jira/browse/HADOOP-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024878#comment-15024878
]
Chris Nauroth commented on HADOOP-12294:
----------------------------------------
If the intent was to remove support from trunk/3.0, then I think all traces of
it should have been removed from the codebase. Right now, I see that
{{FsPermission#DEPRECATED_UMASK_LABEL}} is still present. If that had been
removed, then it also would have forced us to fix the test failures reported in
HDFS-9451. Those test suites would have started getting compilation failures
after removal of {{FsPermission#DEPRECATED_UMASK_LABEL}}.
I propose that we revert the current patch, create a new patch that really
removes all traces from the codebase, and incorporates any test fixes currently
tracked in HDFS-9451. Please let me know if I'm missing some reason that
{{FsPermission#DEPRECATED_UMASK_LABEL}} needs to remain. Thanks!
> Remove the support of the deprecated dfs.umask
> ----------------------------------------------
>
> Key: HADOOP-12294
> URL: https://issues.apache.org/jira/browse/HADOOP-12294
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Reporter: Chang Li
> Assignee: Chang Li
> Fix For: 3.0.0
>
> Attachments: HADOOP-12294.2.patch, HADOOP-12294.patch
>
>
> provide better visibility of parsing configuration failure by logging full
> error message and propagate error message of parsing configuration back to
> client
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
