hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6521) FsPermission:SetUMask not updated to use new-style umask setting.
Date Mon, 01 Feb 2010 23:48:18 GMT

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

Jakob Homan commented on HADOOP-6521:

Setting both is a good approach, but will have the unfortunate side effect that if the user
is correctly using the new key, the old key will also be set and the user will then get undeserved
deprecation warnings.  An offline discussion c/ Nicholas and Suresh suggests that comparing
the values of both the old and new keys may miss some valid cases where a warning is warranted,
but will avoid invalid warnings. This is probably the best approach to take.

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