hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13310) S3A reporting of file group as null is harmful to compatibility for the shell.
Date Wed, 22 Jun 2016 10:43:57 GMT

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

Allen Wittenauer commented on HADOOP-13310:

The usual implementation for file systems that don't support UNIX-style permissions is to
reflect the uid and group of the owner of the current process.  This way permissions checks
"just work" since they are invalid anyway.

> S3A reporting of file group as null is harmful to compatibility for the shell.
> ------------------------------------------------------------------------------
>                 Key: HADOOP-13310
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13310
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Chris Nauroth
>            Priority: Minor
> S3A does not persist group information in file metadata.  Instead, it stubs the value
of the group to an empty string.  Although the JavaDocs for {{FileStatus#getGroup}} indicate
that empty string is a possible return value, this is likely to cause compatibility problems.
 Most notably, shell scripts that expect to be able to perform positional parsing on the output
of things like {{hadoop fs -ls}} will stop working if retargeted from HDFS to S3A.

This message was sent by Atlassian JIRA

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

View raw message