hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-126) Permission configuration files should use octal and symbolic
Date Tue, 18 Aug 2009 15:59:14 GMT

    [ https://issues.apache.org/jira/browse/HDFS-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744570#action_12744570
] 

Owen O'Malley commented on HDFS-126:
------------------------------------

No, it isn't acceptable to break backwards compatability.

Symbolic is ok, since it isn't ambiguous. To use straight octal we either need a flag like
a leading o or use a new attribute and handle the old attribute in decimal.

My other concern in this area is against supporting octal via a leading 0 on all integer attributes.
That will lead to massive confusion, in my opinion.


> 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.


Mime
View raw message