hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1084) updating a hdfs file, doesn't cause the distributed file cache to update itself
Date Thu, 19 Jul 2007 14:52:07 GMT

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

Arun C Murthy updated HADOOP-1084:
----------------------------------

    Attachment: HADOOP-1084_2_20070719.patch

Patch updated due to changes in trunk and added checks to ensure that changes to the files
to be cached on hdfs _after_ job has started are caught, and punished! *smile*

> 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: Arun C Murthy
>            Priority: Blocker
>             Fix For: 0.14.0
>
>         Attachments: HADOOP-1084_1_20070716.patch, HADOOP-1084_2_20070719.patch
>
>
> 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.


Mime
View raw message