[HDFS-711] hdfsUtime does not handle atime = 0 or mtime = 0 correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.1
• Fix Version/s: 2.0.2-alpha
• Component/s: documentation
• Hadoop Flags: Reviewed
• Assignee: Colin McCabe
• Reporter: freestyler
• Created: 16/Oct/09 04:22
• Updated: 11/Oct/12 17:46
• Resolved: 08/Jul/12 18:29

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."