You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2008/09/29 18:37:44 UTC

[jira] Updated: (HADOOP-4299) Unable to access a file by a different user in the same group when permissions is set to 770 or when permissions is turned OFF

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

Nigel Daley updated HADOOP-4299:
--------------------------------

    Priority: Blocker  (was: Minor)

> Unable to access a file by a different user in the same group when permissions is set to 770 or when permissions is turned OFF
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4299
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4299
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.19.0
>            Reporter: Ramya R
>            Priority: Blocker
>             Fix For: 0.19.0
>
>
> Consider the following two scenarios
> 1)   With permissions ON, start cluster as user A, create a file as user A, chmod 770 file as user A, access file as user B(using 'get' command) 
> The expected behavior would be that user B should be able to access the file since user A and user B are in the same group. But this is not happening. Instead the following error message is displayed "get: Permission denied"
> 2)  With permissions ON, start cluster as user A, create a file as user A, chmod 700 file as user A, shut down dfs and turn permissions OFF and start up dfs, access file as user B(using 'get')
> The expected behavior would be that user B should be able to access the file since permissions is turned OFF. But this is not happening. Instead the following error message is displayed "get: Permission denied"

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