[ 
https://issues.apache.org/jira/browse/CASSANDRA-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597775#comment-13597775
 ] 

Dave Brosius commented on CASSANDRA-5201:
-----------------------------------------

{quote} wonder if it would be preferable to have all of the code in tree in the 
same jar still, but have different package paths, like 
org.apache.cassandra.hadoop (for backwards compatibility) and 
org.apache.cassandra.hadoop2. Would that work?{quote}

probably could be done. here's some 'issues' with that approach.

1) external code won't work against both versions with the same code base. 
Obviously the modifications are insignificant, (packages) but still.
2) Makes the build.xml file marginally more complicated as you have to use 
<exclude> elements in the build
3) Building in IDEs is complicated as you need to add resource excludes, since 
these packages need to be built as a separate project (at least one of them 
does).
4) If you have two IDE projects targetting the same classes dir, cleaning one 
project cleans the other.

i could do it either way... whatever people think.

                
> Cassandra/Hadoop does not support current Hadoop releases
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-5201
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5201
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Hadoop
>    Affects Versions: 1.2.0
>            Reporter: Brian Jeltema
>            Assignee: Dave Brosius
>         Attachments: 5201_a.txt
>
>
> Using Hadoop 0.22.0 with Cassandra results in the stack trace below.
> It appears that version 0.21+ changed org.apache.hadoop.mapreduce.JobContext
> from a class to an interface.
> Exception in thread "main" java.lang.IncompatibleClassChangeError: Found 
> interface org.apache.hadoop.mapreduce.JobContext, but class was expected
>       at 
> org.apache.cassandra.hadoop.ColumnFamilyInputFormat.getSplits(ColumnFamilyInputFormat.java:103)
>       at 
> org.apache.hadoop.mapreduce.JobSubmitter.writeNewSplits(JobSubmitter.java:445)
>       at 
> org.apache.hadoop.mapreduce.JobSubmitter.writeSplits(JobSubmitter.java:462)
>       at 
> org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:357)
>       at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1045)
>       at org.apache.hadoop.mapreduce.Job$2.run(Job.java:1042)
>       at java.security.AccessController.doPrivileged(Native Method)
>       at javax.security.auth.Subject.doAs(Subject.java:415)
>       at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1153)
>       at org.apache.hadoop.mapreduce.Job.submit(Job.java:1042)
>       at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1062)
>       at MyHadoopApp.run(MyHadoopApp.java:163)
>       at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:69)
>       at MyHadoopApp.main(MyHadoopApp.java:82)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:601)
>       at org.apache.hadoop.util.RunJar.main(RunJar.java:192)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to