[
https://issues.apache.org/jira/browse/HADOOP-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033499#comment-13033499
]
Nicholas Telford commented on HADOOP-7269:
------------------------------------------
That was actually my initial idea, but thought that it'd stand a better chance
of being accepted if it was more abstract. I see your point though, it's part
of the reason I felt so uneasy about the implementation.
Thanks for the review, I'll refactor the patch for S3 only on Monday.
> 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
>
>
> 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
