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] Updated: (HADOOP-6521) FsPermission:SetUMask not updated to use new-style umask setting.
Date Mon, 01 Feb 2010 22:22:18 GMT

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

Suresh Srinivas updated HADOOP-6521:

    Attachment: hadoop-6521.rel20.patch

Patch for release 20 attached. The approach is:
# To ensure backward compatibility, when applications use the old key "dfs.umask" and the
server default has "dfs.umaskmode", old key overrides the new key. That is first the old key
is used for getting umask and then the new key.
# FsPermission.setUMask(Configuration conf, FsPermission umask) currently has a bug. When
setting the "dfs.umaskmode" param in the configuration, it should convert the umask decimal
value to octal.

This patch is not applicable to release 21, since it uses deprecation mechanism introduced
in Hadoop-6105 and more work is needed to make this solution work in that realm.

> FsPermission:SetUMask not updated to use new-style umask setting.
> -----------------------------------------------------------------
>                 Key: HADOOP-6521
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6521
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Jakob Homan
>         Attachments: hadoop-6521.rel20.patch
> FsPermission:
> 221   /** Set the user file creation mask (umask) */
> 222   public static void setUMask(Configuration conf, FsPermission umask) {         
> 223     conf.setInt(UMASK_LABEL, umask.toShort());
> 224   }
> Needs to be updated to not use a decimal value. This is a bug introduced by HADOOP-6234.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message