Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-711

hdfsUtime does not handle atime = 0 or mtime = 0 correctly

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.20.1
    • Fix Version/s: 2.0.2-alpha
    • Component/s: documentation
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

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

        Attachments

        1. HDFS-711.001.patch
          0.6 kB
          Colin P. McCabe
        2. HDFS-711.002.patch
          2 kB
          Colin P. McCabe
        3. HDFS-711.003.patch
          1 kB
          Colin P. McCabe

          Activity

            People

            • Assignee:
              cmccabe Colin P. McCabe
              Reporter:
              freestyler freestyler
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: