Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1865567009.48281267653507299.JavaMail.jira@brutus.apache.org>
Date: Wed, 3 Mar 2010 21:58:27 +0000 (UTC)
From: "Mahadev konar (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1548) Hadoop archives should be able
 to preserve times and other properties from original files
In-Reply-To: <145022474.3661267521087355.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840908#action_12840908 ] 

Mahadev konar commented on MAPREDUCE-1548:
------------------------------------------

shouldnt we be using the default umask for the part files? and the owner would be the one who runs the archive command. no? Its similar to how you would create a tar!

> Hadoop archives should be able to preserve times and other properties from original files
> -----------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1548
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1548
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: harchive
>            Reporter: Rodrigo Schmidt
>            Assignee: Rodrigo Schmidt
>
> Files inside hadoop archives don't keep their original:
> - modification time
> - access time
> - permission
> - owner
> - group
> all such properties are currently taken from the file storing the archive index, and not the stored files. This doesn't look very correct.
> There should be possible to preserve the original properties of the stored files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.