Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D7245D43C for ; Mon, 9 Jul 2012 13:56:36 +0000 (UTC) Received: (qmail 86028 invoked by uid 500); 9 Jul 2012 13:56:36 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 85780 invoked by uid 500); 9 Jul 2012 13:56:36 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 85716 invoked by uid 99); 9 Jul 2012 13:56:35 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jul 2012 13:56:35 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 679B914285A for ; Mon, 9 Jul 2012 13:56:35 +0000 (UTC) Date: Mon, 9 Jul 2012 13:56:35 +0000 (UTC) From: "Hudson (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <1347672510.22989.1341842195426.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Commented] (HDFS-711) hdfsUtime does not handle atime = 0 or mtime = 0 correctly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409471#comment-13409471 ] Hudson commented on HDFS-711: ----------------------------- Integrated in Hadoop-Mapreduce-trunk-Commit #2452 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2452/]) HDFS-711. hdfsUtime does not handle atime = 0 or mtime = 0 correctly. Contributed by Colin Patrick McCabe (Revision 1358810) Result = FAILURE eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1358810 Files : * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/hdfs.c * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/native/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 > Fix For: 2.0.1-alpha > > Attachments: HDFS-711.001.patch, HDFS-711.002.patch, HDFS-711.003.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