[
https://issues.apache.org/jira/browse/MAPREDUCE-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting resolved MAPREDUCE-1634.
-------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 0.22.0)
> It's pragmatic to package these classes in Avro, but long-term...
Yes, you're right, it's not black and white, but pragmatic. In the past we've
generally encouraged FileSystem and InputFormat implementations to be included
in Hadoop so they're easier to maintain as Hadoop's APIs evolved. However in
this case we have a new InputFormat that we'd like to be able use with older
releases of Hadoop. And we now also expect the Hadoop APIs it uses to be
stable for some time. As Hadoop's APIs stablize we might see more such
user-level "library" code maintained independently from Hadoop.
Closing this as a duplicate of AVRO-493.
> add input and output formats for Avro value wrappers
> ----------------------------------------------------
>
> Key: MAPREDUCE-1634
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1634
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: client
> Reporter: Doug Cutting
> Attachments: MAPREDUCE-1634.patch
>
>
> HADOOP-6660 proposes adding an AvroValue wrapper for Avro data. We should
> add InputFormat and OutputFormat implementations for Avro data files that use
> this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
