You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Jakob Homan (JIRA)" <ji...@apache.org> on 2009/11/26 06:33:40 UTC

[jira] Updated: (HADOOP-6396) Provide a description in the exception when an error is encountered parsing umask

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

Jakob Homan updated HADOOP-6396:
--------------------------------

    Attachment: HADOOP-6396.patch

Patch updates message and test case with more clear explanation of the issue.  Tested against hdfs with new common jar and no problems.  

> Provide a description in the exception when an error is encountered parsing umask
> ---------------------------------------------------------------------------------
>
>                 Key: HADOOP-6396
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6396
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.21.0, 0.22.0
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>             Fix For: 0.21.0, 0.22.0
>
>         Attachments: HADOOP-6396.patch
>
>
> Currently when there is a problem parsing a umask, the exception text is just the offending umask with no other clue, which can be quite confusing as demonstrated in HDFS-763.  This message should include the nature of the problem and whether or not the umask parsing attempt was using old-style or new-style values.

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