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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2007/06/29 02:00:17 UTC

[jira] Commented: (HADOOP-1084) updating a hdfs file, doesn't cause the distributed file cache to update itself

    [ https://issues.apache.org/jira/browse/HADOOP-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508965 ] 

Owen O'Malley commented on HADOOP-1084:
---------------------------------------

With the block-level crc's coming, we should move to filestamps rather than checksums. It is less precise, but the crc information is going away. 

> updating a hdfs file, doesn't cause the distributed file cache to update itself
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-1084
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1084
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.12.0
>            Reporter: Owen O'Malley
>            Assignee: Mahadev konar
>
> If I delete and upload a new version of a file /user/owen/foo to HDFS and start my job with hdfs://user/owen/foo as a cached file, it will use the previous contents.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.