hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11211) mapreduce.job.classloader.system.classes semantics should be order-independent
Date Thu, 11 Dec 2014 21:40:17 GMT

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

Gera Shegalov updated HADOOP-11211:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2. Thanks [~timyitong] for contribution, [~sjlee0] and [~kamrul]
for helping review the patch. 

> mapreduce.job.classloader.system.classes semantics should be order-independent
> ------------------------------------------------------------------------------
>                 Key: HADOOP-11211
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11211
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: hudson
>            Reporter: Yitong Zhou
>            Assignee: Yitong Zhou
>             Fix For: 2.7.0
>         Attachments: HADOOP-11211.003.patch, HADOOP-11211.patch
> If we want to include package foo.bar.* but exclude all sub packages named foo.bar.tar.*
in system classes, configuring "mapreduce.job.classloader.system.classes=foo.bar.,-foo.bar.tar."
won't work. foo.bar.tar will still be pulled in. But if we change the order:
> "mapreduce.job.classloader.system.classes=-foo.bar.tar.,foo.bar.", then it will work.
> This bug is due to the implementation of ApplicationClassLoaser#isSystemClass in hadoop-common,
where we simply return the matching result immediately when the class name hits the first
match (either positive or negative).

This message was sent by Atlassian JIRA

View raw message