hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12390) Enhance FsShell file put to support selectively preserving individual file attributes.
Date Thu, 08 Oct 2015 05:07:28 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948081#comment-14948081
] 

Chris Nauroth commented on HADOOP-12390:
----------------------------------------

Hello [~jagadesh.kiran].  Thanks for picking this up!  Before we proceed, let's see what happens
with HDFS-9208.  If that work proceeds, then this issue might not be relevant anymore.

> Enhance FsShell file put to support selectively preserving individual file attributes.
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12390
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12390
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Chris Nauroth
>            Assignee: Jagadesh Kiran N
>
> {{hadoop fs -put}} currently supports the {{-p}} option.  When used, this option preserves
the source file's access time, modification time, ownership and mode.  If the destination
is HDFS, then this effectively means HDFS must be configured to use modification time.  If
the HDFS deployment chooses to disable access time by setting {{dfs.namenode.accesstime.precision}}
to 0, then attempts to use the {{-p}} flag all fail with "Access time for hdfs is not configured."
 This issue proposes to introduce separate options for preserving just ownership, just mode,
or just times.  For backwards compatibility, the behavior of a bare {{-p}} must continue to
be preserving all 3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message