hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuanbo Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-10276) Different results for exist call for file.ext/name
Date Wed, 20 Apr 2016 09:36:25 GMT

    [ https://issues.apache.org/jira/browse/HDFS-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249555#comment-15249555

Yuanbo Liu commented on HDFS-10276:

[~cmccabe] Thanks for your comment. Yes I agree with you that we should take unprivileged
users as consider. But in this case, NameNode should prevent any further operation since it
knows the "parent path" is a file, not a real path. I think it's more reasonable to throw
{{ParentNotDirectoryException}} rather than {{AccessControlException}}. See the behavior of
Linux as below:
[yuanbo@oc7702007844 ~]$ ls test/test1
ls: cannot access test/test1: Not a directory
One thing should be rectified is that {{getFileInfo}} in {{DFSClient}}  causes this problem
instead of {{exists}} method.

> Different results for exist call for file.ext/name
> --------------------------------------------------
>                 Key: HDFS-10276
>                 URL: https://issues.apache.org/jira/browse/HDFS-10276
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Kevin Cox
>            Assignee: Yuanbo Liu
> Given you have a file {{/file}} an existence check for the path {{/file/whatever}} will
give different responses for different implementations of FileSystem.
> LocalFileSystem will return false while DistributedFileSystem will throw {{org.apache.hadoop.security.AccessControlException:
Permission denied: ..., access=EXECUTE, ...}}

This message was sent by Atlassian JIRA

View raw message