[
https://issues.apache.org/jira/browse/HADOOP-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034725#comment-13034725
]
Hadoop QA commented on HADOOP-7269:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12479451/HADOOP-7269-S3-metadata-003.diff
against trunk revision 1103971.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 9 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 1070 javac compiler warnings (more
than the trunk's current 1068 warnings).
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/465//testReport/
Findbugs warnings:
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/465//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/465//console
This message is automatically generated.
> 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
