[jira] [Commented] (HADOOP-13309) Document S3A known limitations in file ownership and permission model.

["Chris Nauroth (JIRA)" <ji...@apache.org>]

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

Chris Nauroth commented on HADOOP-13309:
----------------------------------------

Limitations as of right now:

# There is no notion of separate identity for different users.  Once a user is authenticated to the S3 bucket, they effectively have full access to the file system tree.
# The file owner is always reported as the user running the current process.
# The group is always null (no group associated).
# Permissions are always 777 for directories and 666 for files.
# S3A performs no actual checks on the permissions.   It's just authentication to the entire S3 bucket, based on AWS credentials.  It's possible that object ACLs are applied, but this is something enforced entirely within S3, not a feature of S3A.


> Document S3A known limitations in file ownership and permission model.
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-13309
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13309
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Chris Nauroth
>            Priority: Minor
>
> S3A does not match the implementation of HDFS in its handling of file ownership and permissions.  Fundamental S3 limitations prevent it.  This is a frequent source of confusion for end users.  This issue proposes to document these known limitations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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