[
https://issues.apache.org/jira/browse/AVRO-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213866#comment-13213866
]
Doug Cutting commented on AVRO-593:
-----------------------------------
> Ideally, anything in the .io, .util, and .file packages does not reference
> the .mapred or .mapreduce packages [ ... ]
Much in these packages references AvroKey and AvroValue and/or AvroJob. These
uses aren't mapreduce-specific and could be refactored away, e.g., by moving
AvroKey and AvroValue from o.a.a.mapred to o.a.a.hadoop.io, but that would be
incompatible.
SortedKeyValueFile is the Avro equivalent of Hadoop's MapFile. Arguably it
should be moved into o.a.a.io. It depends on AvroKeyValue, which might also be
moved to the core. AvroKeyValue is very similar in functionality to
o.a.a.mapred.Pair. Perhaps SortedKeyValueFile should be switched to use Pair
and both moved to the core.
I have implemented a SequenceFile shim and it works. There's now just a tiny
class that needs to be in o.a.h.io, a base class that exposes two
package-private nested classes from within SequenceFile.
I've re-arranged the classes per Scott's #4 variant but can revert that. We
need to decide how much refactoring we want to do here.
Finally, I note that io.SeekableHadoopInput replicates functionality that's
already in mapred.FsInput, so we should replace the former with the latter in
the new code.
> Avro mapreduce apis incompatible with hadoop 0.20.2
> ---------------------------------------------------
>
> Key: AVRO-593
> URL: https://issues.apache.org/jira/browse/AVRO-593
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.3.2, 1.3.3
> Environment: Avro 1.3.3, Hadoop 0.20.2
> Reporter: Steve Severance
> Assignee: Garrett Wu
> Attachments: AVRO-593.patch, AVRO-593.patch
>
>
> The avro api's for hadoop use the hadoop mapreduce api that has been
> deprecated. A new avro mapreduce api should be implemented for hadoop 0.20
> and higher.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
