hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9737) JarFinder#getJar should delete the jar file upon destruction of the JVM
Date Fri, 08 May 2015 23:09:07 GMT

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

Robert Kanter updated HADOOP-9737:
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.8.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Thanks [~jbonofre] for the patch and [~kiranmr] for the review.  Committed to trunk and branch-2!

> JarFinder#getJar should delete the jar file upon destruction of the JVM
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-9737
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9737
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 2.0.0-alpha
>            Reporter: Esteban Gutierrez
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.8.0
>
>         Attachments: HADOOP-9737.patch
>
>
> Once {{JarFinder.getJar()}} is invoked by a client app, it would be really useful to
destroy the generated JAR after the JVM is destroyed by setting {{tempJar.deleteOnExit()}}.
In order to preserve backwards compatibility a configuration setting could be implemented,
e.g. {{test.build.dir.purge.on.exit}}



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

Mime
View raw message