Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF7F14D04 for ; Fri, 17 Jun 2011 17:39:09 +0000 (UTC) Received: (qmail 70173 invoked by uid 500); 17 Jun 2011 17:39:09 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 70073 invoked by uid 500); 17 Jun 2011 17:39:08 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 69851 invoked by uid 99); 17 Jun 2011 17:39:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2011 17:39:08 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jun 2011 17:39:07 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 8DE8D41E98E for ; Fri, 17 Jun 2011 17:38:47 +0000 (UTC) Date: Fri, 17 Jun 2011 17:38:47 +0000 (UTC) From: "Nicholas Telford (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1179062691.15731.1308332327578.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1117582463.32721.1304959323395.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HADOOP-7269) S3 Native should allow customizable file meta-data (headers) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicholas Telford updated HADOOP-7269: ------------------------------------- Attachment: 7269-combined-002.patch Fixed 2 additional compiler warnings. Thanks Todd for helping me track them down. > 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, 7269-combined-002.patch, 7269-combined-proper.patch, 7269-combined.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: > * Content-MD5: > 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