Return-Path: 
 <common-issues-return-15998-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 2D56646AE
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Wed,  8 Jun 2011 16:40:22 +0000 (UTC)
Received: (qmail 55163 invoked by uid 500); 8 Jun 2011 16:40:22 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 55127 invoked by uid 500); 8 Jun 2011 16:40:22 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 55119 invoked by uid 99); 8 Jun 2011 16:40:21 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jun 2011 16:40:21 +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; Wed, 08 Jun 2011 16:40:19 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id DBADB1081BE
	for <common-issues@hadoop.apache.org>; Wed,  8 Jun 2011 16:39:58 +0000 (UTC)
Date: Wed, 8 Jun 2011 16:39:58 +0000 (UTC)
From: "Nicholas Telford (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <906288486.3686.1307551198896.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
X-Virus-Checked: Checked by ClamAV on apache.org


     [ 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