[
https://issues.apache.org/jira/browse/HADOOP-11211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218490#comment-14218490
]
Gera Shegalov commented on HADOOP-11211:
----------------------------------------
[~timyitong] MAPREDUCE-6128 is not committed, so you must have some leftovers
from your local repo if you tried it out at some point. I recommend that you
create a branch for each JIRA to avoid mixups. It's probably better if you
could work with Apache Git directly to have the latest trunk. Then you could
have your JIRA patch branches track the upstream trunk:
{code}
git branch --set-upstream-to=git branch
--set-upstream-to=apache-git/trunk/trunk
{code}
where apache-git is a remote for the Apache repo. Then you can easily {{git
pull --rebase}} to refresh your patch
> 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
> Affects Versions: hudson
> Reporter: Yitong Zhou
> Assignee: Yitong Zhou
> Fix For: hudson
>
> 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)
