[
https://issues.apache.org/jira/browse/HDFS-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173999#comment-13173999
]
Uma Maheswara Rao G commented on HDFS-2712:
-------------------------------------------
Agreed, we should leave mtime, as we are capturing the mtime while creating.
Also we will access the API getModficationTime api from INode, while logging
the mkdir op into Editlog.
Nicholas, what do you say?
> setTimes should support only for files and move the mtime&atime fields down
> to iNodeFile.
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-2712
> URL: https://issues.apache.org/jira/browse/HDFS-2712
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0, 0.24.0
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
>
> After the dicussion in HDFS-2436, unsupported behaviour for setTimes was
> intentional (HADOOP-1869).
> But current INode structure hierarchy seems, it supports atime and mtime for
> directories also. But as per HADOOP-1869, we are supporting only for files.
> To avoid the confusions, we can move the mtime and atime fields to INodeFile
> as we planned to support setTimes only for files. And also restrict the
> support for setTimes on directories ( which is implemented with HDFS-2436 ).
--
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
