[
https://issues.apache.org/jira/browse/HDFS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HDFS-1772:
-----------------------------------------
Attachment: TestListPathServlet.patch
TestListPathServlet.patch: Here a test illustrating the bug.
Below are the log generated with the test. Note that "expected" and "computed"
are obtained from {{hdfs://}} and {{hftp://}}, respectively.
{noformat}
2011-03-21 21:23:51,213 INFO fs.FileSystem
(TestListPathServlet.java:checkFileStatus(189)) - expected.getAccessTime() =
1300742630691
2011-03-21 21:23:51,214 INFO fs.FileSystem
(TestListPathServlet.java:checkFileStatus(190)) - computed.getAccessTime() =
1300742630000
2011-03-21 21:23:51,214 INFO fs.FileSystem
(TestListPathServlet.java:checkFileStatus(191)) -
expected.getModificationTime() = 1300742631173
2011-03-21 21:23:51,214 INFO fs.FileSystem
(TestListPathServlet.java:checkFileStatus(192)) -
computed.getModificationTime() = 1300742631000
{noformat}
> atime and mtime are different from hdfs:// and hftp://
> ------------------------------------------------------
>
> Key: HDFS-1772
> URL: https://issues.apache.org/jira/browse/HDFS-1772
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Reporter: Tsz Wo (Nicholas), SZE
> Attachments: TestListPathServlet.patch
>
>
> When two file statuses respectively obtained from {{hdfs://}} and {{hftp://}}
> with an identical path, the access time values and the modification time
> values could be different from these two file statuses.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
