[
https://issues.apache.org/jira/browse/HADOOP-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yitong Zhou updated HADOOP-11211:
---------------------------------
Attachment: HADOOP-11211.patch
I'm having troubles in successfully running all tests in my local repo.
(Getting errors related with Kerberos and authentication. Feels like I need
some more time to figure out how to fix it.)
I did test it with the class alone and succeeded. Should I try fix my local
test environment before trying to run the patch Hudson?
Also it seems like dev-support/test-patch.sh does not work either, my guess is
because of the same reason "mvn test" fails.
> mapreduce.job.classloader.system.classes property behaves differently when
> the exclusion and inclusion order is different
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-11211
> URL: https://issues.apache.org/jira/browse/HADOOP-11211
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Yitong Zhou
> Assignee: Yitong Zhou
> Attachments: 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
(v6.3.4#6332)
