[HADOOP-11211] mapreduce.job.classloader.system.classes semantics should be order-independent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: hudson
• Fix Version/s: 2.7.0
• Assignee: Yitong Zhou
• Reporter: Yitong Zhou
• Created: 18/Oct/14 01:08
• Updated: 24/Apr/15 22:49
• Resolved: 11/Dec/14 21:40

Description

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).

Issue Links

• is duplicated by: MAPREDUCE-5802 Provide an inclusion list mapreduce.job.classloader.job.classes for the class loading isolation