You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/11/17 22:40:44 UTC

[jira] Commented: (HADOOP-4669) A file-open sometimes may not set the access time of a file

    [ https://issues.apache.org/jira/browse/HADOOP-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648356#action_12648356 ] 

Raghu Angadi commented on HADOOP-4669:
--------------------------------------

patch looks fine. But I don't think this is a bug fix since end result of "logical AND (&)" and "conditional AND (&&)" is exactly same. It is just that second condition will always be evaluated in this case of '&'. 

+1 for the patch, though.


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