I have a long rant at http://lordjoesoftware.blogspot.com/ on this but the moral is that there seems to have been a deliberate decision that 0,20 code will may not be comparable with - I have NEVER seen a major library so directly abandon backward compatability
On Fri, Nov 12, 2010 at 8:04 AM, Sebastian Schoenherr < sebastian.schoenh...@student.uibk.ac.at> wrote: > Hi Steve, > we had a similar problem. We've compiled our code with version 0.21 but > included the wrong jars into the classpath. (version 0.20.2; > NInputFormat.java). It seems that Hadoop changed this class to an interface, > maybe you've a simliar problem. > Hope this helps. > Sebastian > > > Zitat von Steve Lewis <lordjoe2...@gmail.com>: > > > Cassandra sees this error with 0.21 of hadoop >> >> Exception in thread "main" java.lang.IncompatibleClassChangeError: Found >> interface org.apache.hadoop.mapreduce.JobContext, but class was expected >> >> I see something similar >> Error: Found interface org.apache.hadoop.mapreduce.TaskInputOutputContext, >> but class was expected >> >> I find this especially puzzling >> since org.apache.hadoop.mapreduce.TaskInputOutputContext IS a class not an >> interface >> >> Does anyone have bright ideas??? >> >> -- >> Steven M. Lewis PhD >> 4221 105th Ave Ne >> Kirkland, WA 98033 >> 206-384-1340 (cell) >> Institute for Systems Biology >> Seattle WA >> >> > > > -- Steven M. Lewis PhD 4221 105th Ave Ne Kirkland, WA 98033 206-384-1340 (cell) Institute for Systems Biology Seattle WA
