[
https://issues.apache.org/jira/browse/HADOOP-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Telford updated HADOOP-7269:
-------------------------------------
Status: Patch Available (was: Open)
This patch only allows the writing of metadata for a new file. You cannot
arbitrarily add metadata for an existing file, nor can you read existing
metadata.
The major use-case for this is so that you can provide S3 with instructions
about the file (e.g. Expires, Content-Disposition, etc.) so it's not actually
as useless as it sounds.
> 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:
> 0001-Added-support-for-metadata-to-be-applied-to-objects-.patch,
> 0002-Added-check-that-metadata-was-set-to-unit-test.patch,
> 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
