hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6234) Permission configuration files should use octal and symbolic
Date Fri, 20 Nov 2009 17:44:39 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780673#action_12780673

Suresh Srinivas commented on HADOOP-6234:

For 0.20 patch, the problem described in HDFS-760 is not relevant. On trunk we use a different
backward compatibility mechanism to map deprecated configuration key to new configuration
key, using DeprecatedKeyInfo. That patch has its own mechanism to provide backward compatibility.

> Permission configuration files should use octal and symbolic
> ------------------------------------------------------------
>                 Key: HADOOP-6234
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6234
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Allen Wittenauer
>            Assignee: Jakob Homan
>             Fix For: 0.21.0
>         Attachments: COMMON-126.patch, COMMON-6234.patch, COMMON-6234.rel20.1.patch,
COMMON-6234.rel20.patch, COMMON-6234.rel20.patch
> 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.

View raw message