Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 11 Sep 2017 14:08:00 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12506632.1304959297000.78949.1505138880981@Atlassian.JIRA>
In-Reply-To: <JIRA.12506632.1304959297000@Atlassian.JIRA>
References: <JIRA.12506632.1304959297000@Atlassian.JIRA> <JIRA.12506632.1304959297761@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (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
archived-at: Mon, 11 Sep 2017 14:08:06 -0000


     [ https://issues.apache.org/jira/browse/HADOOP-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved HADOOP-7269.
------------------------------------
    Resolution: Won't Fix

Resolving as a WONTFIX as we are going to cull s3n. however, being able to set headers is something I think I'd like to do, somehow. Maybe we could do it with the new builder API for opening files....we could let callers declare the headers as options when the file is opened. 

> 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.patch, 7269-combined-proper.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 was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org