You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Stefan De Smit (JIRA)" <ji...@apache.org> on 2013/11/15 14:59:21 UTC
[jira] [Created] (CRUNCH-295)
java.lang.IncompatibleClassChangeError: Found class
org.apache.hadoop.mapreduce.TaskInputOutputContext, but interface was
expected in crunch 0.8.0
Stefan De Smit created CRUNCH-295:
-------------------------------------
Summary: java.lang.IncompatibleClassChangeError: Found class org.apache.hadoop.mapreduce.TaskInputOutputContext, but interface was expected in crunch 0.8.0
Key: CRUNCH-295
URL: https://issues.apache.org/jira/browse/CRUNCH-295
Project: Crunch
Issue Type: Bug
Components: Core
Affects Versions: 0.8.0
Reporter: Stefan De Smit
Assignee: Josh Wills
Crunch 0.8.0 does not work for me, while crunch 0.7.0 did.
To be more precise: when I compile crunch 0.8.0 from the git tag, it does work, but the jars downloaded from Maven Central don't.
I compared both jars (mine vs downloaded) and they are indeed different.
you can see (for instance in CrunchTaskContext):
invokevirtual #4; //Method org/apache/hadoop/mapreduce...
vs
invokeinterface #4, 1; //InterfaceMethod org/apache/hadoop/mapreduce...
Which means that crunch 0.8.0 is compiled with an interface iso an abstract class.
the hadoop-1 profile shows a dependency to hadoop 1.1.2 which contains a class iso an interface.
What we think happened is this:
1) compile crunch with hadoop-2 profile:
2) on same machine also compile crunch with hadoop-1 profile, but without clean option.
because of the missing clean, maven won't recompile unchanged classes. which would explain how you end up with crunch 0.8.0 being compiled against hadoop-2 instead of hadoop-1
--
This message was sent by Atlassian JIRA
(v6.1#6144)