[
https://issues.apache.org/jira/browse/GORA-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967565#comment-13967565
]
Renato Javier Marroquín Mogrovejo commented on GORA-144:
--------------------------------------------------------
Hi [~hsaputra],
For sure that is a good enough reason ;)
During ApacheCon, the idea of making Gora more independent from Hadoop
MapReduce came around. I think this makes sense specially when trying to
integrate with other open source projects (Phoenix, Drill, Flume, Spark, etc)
which just need a way to get/put the data into different data stores but which
are not probably going to be using Hadoop MapReduce for their own tasks.
I will try to write this long email that I have in my head this weekend, so we
can discuss it at length over there :)
> Upgrade gora so to be compatible with hadoop 2
> ----------------------------------------------
>
> Key: GORA-144
> URL: https://issues.apache.org/jira/browse/GORA-144
> Project: Apache Gora
> Issue Type: Task
> Components: avro, build process, maven
> Affects Versions: 0.2
> Reporter: raf shin
> Priority: Minor
> Fix For: 0.4
>
>
> TaskAttemptContext and JobContext which were a class in previous hadoop
> versions are now interfaces.
> Compiling gora with new hadoop version 2 fails.
> BinaryDecoder and BinaryEncoder in Avro 1.5.4 are also now interfaces which
> were previously class.
> avro.ipc.ByteBufferOutputStream and avro.ipc.ByteBufferInputStream are also
> moved to avro.util package.
> There might be much more incompatibilities there which we have not seen yet.
> We gave up upgrading our nutchgora to the new hadoop 2 version.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
