[
https://issues.apache.org/jira/browse/MAPREDUCE-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gera Shegalov updated MAPREDUCE-6128:
-------------------------------------
Attachment: MAPREDUCE-6128.v06.patch
Thanks for your suggestions, [~jlowe].
I will file another JIRA for nested class handling. I got around the issue in
this v06 by filtering the contents of the test jar.
The code is refactored to take care of both libjars and preconfigured cache
jars at the same time. I added a test for this overrides as well.
> Automatic addition of bundled jars to distributed cache
> --------------------------------------------------------
>
> Key: MAPREDUCE-6128
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6128
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Affects Versions: 2.5.1
> Reporter: Gera Shegalov
> Assignee: Gera Shegalov
> Attachments: MAPREDUCE-6128.v01.patch, MAPREDUCE-6128.v02.patch,
> MAPREDUCE-6128.v03.patch, MAPREDUCE-6128.v04.patch, MAPREDUCE-6128.v05.patch,
> MAPREDUCE-6128.v06.patch
>
>
> On the client side, JDK adds Class-Path elements from the job jar manifest
> on the classpath. In theory there could be many bundled jars in many
> directories such that adding them manually via libjars or similar means to
> task classpaths is cumbersome. If this property is enabled, the same jars are
> added
> to the task classpaths automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
