[
https://issues.apache.org/jira/browse/MAPREDUCE-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561473#comment-14561473
]
Guozhang Wang commented on MAPREDUCE-1700:
------------------------------------------
Hello,
We are seeing some similar issues in Samza usage and trying to borrow some
ideas from Hadoop. I read through this ticket and YARN-286 but am still trying
to figure out how it resolves the (e.g. Avro) conflict? For us we have a single
thread that is similar to JobImpl executing user code like map/reduce as well
as some system logic such as ser-de. Let's say we have a Avro 1.4 jar in
CLASSPATH and another Avro 1.7 jar in APP_CLASSPATH. The task's
ApplicationClassLoader would then first load Avro 1.7 from CLASSPATH, but then
when it needs Avro 1.4 for ser-de it will fail because it has already loaded
Avro 1.7 which is backward incompatible. Am I missing anything here?
> User supplied dependencies may conflict with MapReduce system JARs
> ------------------------------------------------------------------
>
> Key: MAPREDUCE-1700
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1700
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: task
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 2.0.3-alpha
>
> Attachments: MAPREDUCE-1700-ccl.patch, MAPREDUCE-1700-ccl.patch,
> MAPREDUCE-1700.patch, MAPREDUCE-1700.patch, MAPREDUCE-1700.patch,
> MAPREDUCE-1700.patch, MAPREDUCE-1700.patch, MAPREDUCE-1700.patch,
> MAPREDUCE-1700.patch, MAPREDUCE-1700.patch
>
>
> If user code has a dependency on a version of a JAR that is different to the
> one that happens to be used by Hadoop, then it may not work correctly. This
> happened with user code using a different version of Avro, as reported
> [here|https://issues.apache.org/jira/browse/AVRO-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852081#action_12852081].
> The problem is analogous to the one that application servers have with WAR
> loading. Using a specialized classloader in the Child JVM is probably the way
> to solve this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
