[
https://issues.apache.org/jira/browse/AVRO-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-593:
------------------------------
Attachment: AVRO-593.patch
I looked at this again today.
AvroKeyValue is similar to Pair but is implemented quite differently. Rather
than itself having 'key' and 'value' fields it wraps a GenericData.Record that
has those two fields. This is exposed in its APIs. Converting its uses to
Pair would thus be a major undertaking. Rather I think we might just tolerate
these two similar classes in the project.
I'm also no longer convinced that it's worth trying to move SortedKeyValueFile
into Avro's core. The reader & writer constructors are Hadoop Path-based and
changing this would require inventing a new abstract file interface, since the
implementation manipulates the file names.
So I just implemented the one other change contemplated in my previous comment
(replacing SeekableHadoopInput with the existing FsInput). Here's a new patch
with that.
Does anyone object to committing this?
> 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, 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
