hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-5470) RunJar.unJar() should write the last modified time found in the jar entry to the uncompressed file
Date Tue, 26 Apr 2016 16:42:13 GMT

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

Arpit Agarwal commented on HADOOP-5470:
---------------------------------------

Hi [~boky01], thanks for updating the patch. Yes this is what I meant.

One more thing I missed last time - we should invoke setLastModified after closing the file.
setLastModified may fail for open files on some platforms.

> RunJar.unJar() should write the last modified time found in the jar entry to the uncompressed
file
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5470
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5470
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1
>            Reporter: Colin Evans
>            Assignee: Andras Bokor
>            Priority: Minor
>              Labels: newbie
>         Attachments: HADOOP-5470.01.patch, HADOOP-5470.02.patch, HADOOP-5470.03.patch,
HADOOP-5470.04.patch, HADOOP-5470.05.patch
>
>
> For tools like jruby and jython, last modified times determine if a script gets recompiled.
 Losing the correct last modified time causes some unfortunate recompilation race conditions
when a job is running.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message