[
https://issues.apache.org/jira/browse/HADOOP-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649428#action_12649428
]
Tsz Wo (Nicholas), SZE commented on HADOOP-4669:
------------------------------------------------
> But I don't think this is a bug fix ...
If someone changes isAccessTimeSupported() and introduces a side effect in the
future, then "logical AND (&)" and "conditional AND (&&)" are no longer the
same. Also, the performance of them are different. I would argue that this is
a bug although no problems would emerge at this moment.
> A file-open sometimes may not set the access time of a file
> -----------------------------------------------------------
>
> Key: HADOOP-4669
> URL: https://issues.apache.org/jira/browse/HADOOP-4669
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Fix For: 0.19.1
>
> Attachments: setTimesBug.patch
>
>
> The access time of a file may not be set even when the file is opened for
> read. This is because FileSystem.getBlockLocationsInternal may not correctly
> evaluate the condition that checks whether "access time" is enabled or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
