You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2016/06/22 16:04:58 UTC
[jira] [Updated] (HADOOP-13310) S3A reporting of file group as
empty is harmful to compatibility for the shell.
[ https://issues.apache.org/jira/browse/HADOOP-13310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Nauroth updated HADOOP-13310:
-----------------------------------
Summary: S3A reporting of file group as empty is harmful to compatibility for the shell. (was: S3A reporting of file group as null is harmful to compatibility for the shell.)
> S3A reporting of file group as empty 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
(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