[jira] [Updated] (HADOOP-12294) Invalid fs.permissions.umask-mode setting should throw an error

["Jason Lowe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated HADOOP-12294:
--------------------------------
             Summary: Invalid fs.permissions.umask-mode setting should throw an error  (was: propagate parsing configuration error to client)
    Target Version/s: 3.0.0
         Component/s: conf

To me this looks like a bug introduced by HADOOP-6521.  It has the confusing behavior that if one tries unsuccessfully to set the new property but the old property has a valid setting, rather than complaining about the bad value it silently falls back to the old property setting.  So users can think they set the property when in reality that setting was ignored unless they watched the logs very closely to notice the warning message.

However it's been this way for a very long time, which makes it hard to reason whether anyone has relied on this unintuitive behavior intentionally or otherwise.  So in that sense I agree with zhihai and Allen that we can avoid any potential breakage in 2.x and propose we fix this for 3.x.

> Invalid fs.permissions.umask-mode setting should throw an error
> ---------------------------------------------------------------
>
>                 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
>         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)