[
https://issues.apache.org/jira/browse/HADOOP-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15024919#comment-15024919
]
Chris Nauroth commented on HADOOP-12294:
----------------------------------------
[~lichangleo], thanks for the clarification about the original intent of the
patch.
Is it worth considering fully eliminating {{dfs.umask}} from trunk? We're
already at a point where the change is backwards-incompatible. It has been
deprecated for a long time in 2.x, so maybe it's time just to remove the whole
thing?
If not, then I think we need to correct this JIRA title and its CHANGES.txt
entry to avoid confusion. Reading the title made me think that {{dfs.umask}}
would stop working altogether.
> 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)
