[
https://issues.apache.org/jira/browse/HADOOP-16613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498806#comment-17498806
]
Brais Couce commented on HADOOP-16613:
--------------------------------------
Hi,
The information of this ticket says that this is resolved in 3.3.0 version as
part of HADOOP-16823. I have tested it and the directory created in S3 does not
have contentType = application/x-directory. In [this
commit|https://github.com/apache/hadoop/pull/1826/commits/86fd17d3687f93e30e58a8bcb13650e77736965f]
the contentType is set but in [this
commit|http://https://github.com/apache/hadoop/pull/1826/commits/86fd17d3687f93e30e58a8bcb13650e77736965f]
it was reverted. Is there any reason for it?
Regards.
> s3a to set fake directory marker contentType to application/x-directory
> -----------------------------------------------------------------------
>
> Key: HADOOP-16613
> URL: https://issues.apache.org/jira/browse/HADOOP-16613
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.1, 3.1.3
> Reporter: Jose Torres
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 3.3.0
>
>
> S3AFileSystem doesn't set a contentType for fake directory files, causing it
> to be inferred as "application/octet-stream". But fake directory files
> created through the S3 web console have content type
> "application/x-directory". We may want to adopt the web console behavior as a
> standard, since some systems will rely on content type and not size +
> trailing slash to determine if an object represents a directory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
