[
https://issues.apache.org/jira/browse/HDFS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744665#action_12744665
]
Jakob Homan commented on HDFS-126:
----------------------------------
I'd guess the massive confusion at this point would be that we're using decimal
rather than octal, but yeah, changing at this point cold-turkey would probably
just confuse a our established users rather than our new users. My concern
over using a lead 0 is that li/unix only uses octal for chmod, whether or not a
leading 0 is specified. I'd like to end up with something that matches that
behavior.
In that case, the best thing is probably to deprecate the current key and
introduce a new one with octal/symbolic semantics. That's the approach I'll
plan on using. Too bad HADOOP-6105 isn't up and runnning yet.
> Permission configuration files should use octal and symbolic
> ------------------------------------------------------------
>
> Key: HDFS-126
> URL: https://issues.apache.org/jira/browse/HDFS-126
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Allen Wittenauer
> Assignee: Jakob Homan
>
> Currently, the settings for the default umask in Hadoop configuration files
> require the input format be in decimal. Considering that every admin in the
> world thinks of permissions in octal and/or symbolic format, the config files
> should really use those two formats and drop decimal.
> [... and, yes, I'm aware this breaks backwards compatibility. But in this
> case, I think that is perfectly acceptable.]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
