[ https://issues.apache.org/jira/browse/HADOOP-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036412#comment-13036412
]
Todd Lipcon commented on HADOOP-7269:
-------------------------------------
hmm, Suresh, are you looking at HADOOP-7269-S3-metadata-003.diff? I don't see changes to FileSystem.java
> S3 Native should allow customizable file meta-data (headers)
> ------------------------------------------------------------
>
> Key: HADOOP-7269
> URL: https://issues.apache.org/jira/browse/HADOOP-7269
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Reporter: Nicholas Telford
> Assignee: Nicholas Telford
> Priority: Minor
> Attachments: HADOOP-7269-S3-metadata-001.diff, HADOOP-7269-S3-metadata-002.diff,
HADOOP-7269-S3-metadata-003.diff
>
>
> The S3 Native FileSystem currently writes all files with a set of default headers:
> * Content-Type: binary/octet-stream
> * Content-Length: <computed from object size>
> * Content-MD5: <computed from object data>
> This is a good start, however many applications would benefit from the ability to customize
(for example) the Content-Type and Expires headers for the file. Ideally the implementation
should be abstract enough to customize all of the available S3 headers and provide a facility
for other FileSystems to specify optional file metadata.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|