You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2012/07/06 20:38:34 UTC
[jira] [Updated] (HDFS-711) hdfsUtime does not handle atime = 0 or
mtime = 0 correctly
[ https://issues.apache.org/jira/browse/HDFS-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colin Patrick McCabe updated HDFS-711:
--------------------------------------
Description:
in HADOOP/src/c++/libhdfs/hdfs.h
The following function document is incorrect:
/* @param mtime new modification time or 0 for only set access time in seconds
@param atime new access time or 0 for only set modification time in seconds
*/
int hdfsUtime(hdfsFS fs, const char* path, tTime mtime, tTime atime);
Currently, setting mtime or atime to 0 has no special meaning. That is, file last modified time will change to 0 if the mtime argument is 0.
libhdfs should translate mtime = 0 or atime = 0 to the special value -1, which in HDFS means "don't change this time."
was:
in HADOOP/src/c++/libhdfs/hdfs.h
The following function document is incorrect:
/* @param mtime new modification time or 0 for only set access time in seconds
@param atime new access time or 0 for only set modification time in seconds
*/
int hdfsUtime(hdfsFS fs, const char* path, tTime mtime, tTime atime);
Setting mtime or atime to 0 has no special meaning. That is, file last modified time will change to 0 if the mtime argument is 0.
Summary: hdfsUtime does not handle atime = 0 or mtime = 0 correctly (was: incorrect document in libhdfs api (hdfs.h))
> hdfsUtime does not handle atime = 0 or mtime = 0 correctly
> ----------------------------------------------------------
>
> Key: HDFS-711
> URL: https://issues.apache.org/jira/browse/HDFS-711
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.20.1
> Reporter: freestyler
> Assignee: Colin Patrick McCabe
> Attachments: HDFS-711.001.patch
>
>
> in HADOOP/src/c++/libhdfs/hdfs.h
> The following function document is incorrect:
> /* @param mtime new modification time or 0 for only set access time in seconds
> @param atime new access time or 0 for only set modification time in seconds
> */
> int hdfsUtime(hdfsFS fs, const char* path, tTime mtime, tTime atime);
> Currently, setting mtime or atime to 0 has no special meaning. That is, file last modified time will change to 0 if the mtime argument is 0.
> libhdfs should translate mtime = 0 or atime = 0 to the special value -1, which in HDFS means "don't change this time."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira