[
https://issues.apache.org/jira/browse/HADOOP-7264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087420#comment-13087420
]
Alejandro Abdelnur commented on HADOOP-7264:
--------------------------------------------
I'm OK either way.
Actually I prefer your approach (I didn't see your first patch until I've
uploaded my first version).
My motivation for doing the way it is in my patches was that I'm trying to be
as little invasive as possible for all Mavenization changes, seen many things
that could be done better by rearranging things. I just didn't want to add more
noise than the strictly necessary during the Mavenization.
But, if strong about doing this for this JIRA, I can update the patch.
> Bump avro version to at least 1.4.1
> -----------------------------------
>
> Key: HADOOP-7264
> URL: https://issues.apache.org/jira/browse/HADOOP-7264
> Project: Hadoop Common
> Issue Type: Improvement
> Components: io
> Affects Versions: 0.21.0
> Reporter: Luke Lu
> Assignee: Luke Lu
> Labels: avro
> Fix For: 0.23.0
>
> Attachments: HADOOP-7264v2.patch, HADOOP-7264v3.patch,
> HADOOP-7264v4.patch, hadoop-7264-mr2-v1.patch, hadoop-7264-v1.patch
>
>
> Needed by mapreduce 2.0 avro support. Maybe we could jump to Avro 1.5. There
> is incompatible API changes from 1.3x to 1.4x (Utf8 to CharSequence in user
> facing APIs) not sure about 1.5x though.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
