hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14843) FsPermission symbolic parsing failed to detect invalid argument
Date Wed, 06 Sep 2017 20:01:00 GMT

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

Jason Lowe commented on HADOOP-14843:
-------------------------------------

I believe HADOOP-13508 triggered the behavior change from interpreting the malformed argument
as mode 0000 instead of mode 0777.  However I wouldn't say this bug was caused by that JIRA.
 The FsPermission string constructor was accepting this malformed argument both before and
after HADOOP-13508, and it should have thrown an error in either case.

> FsPermission symbolic parsing failed to detect invalid argument
> ---------------------------------------------------------------
>
>                 Key: HADOOP-14843
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14843
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.7.4, 2.8.1
>            Reporter: Jason Lowe
>            Assignee: Bharat Viswanadham
>
> A user misunderstood the syntax format for the FsPermission symbolic constructor and
passed the argument "-rwr" instead of "u=rw,g=r".  In 2.7 and earlier this was silently misinterpreted
as mode 0777 and in 2.8 it oddly became mode 0000.  In either case FsPermission should have
flagged "-rwr" as an invalid argument rather than silently misinterpreting it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message