[
https://issues.apache.org/jira/browse/HADOOP-12390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-12390:
-----------------------------------
Description: {{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. (was: {{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 modification 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.)
> 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
>
> {{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)
