hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15477) Make unjar in RunJar overrideable
Date Tue, 22 May 2018 09:11:00 GMT

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

Steve Loughran commented on HADOOP-15477:

bq Reason for no test is due to it's simplicity.

the challenge is therefore to find an equally simple test which not only shows the new feature
works, but stops us accidentally breaking it in future

> Make unjar in RunJar overrideable
> ---------------------------------
>                 Key: HADOOP-15477
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15477
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 2.8.3, 2.9.1, 2.7.6, 3.0.2
>            Reporter: Johan Gustavsson
>            Priority: Trivial
>         Attachments: HADOOP-15477.001.patch, HADOOP-15477.002.patch
> Currently Hadoop's RunJar will unjar the jar provided and look for any jars inside and
add them to the classpath. Since most deployments doesn't use jar in jar, but rather uberjars
this could be rather time consuming at times and can cause issues related to over consumption of
inodes, for something that is in many cases is not used.
> For that purpose there should be an env variable to disable this behavior.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message