[
https://issues.apache.org/jira/browse/AVRO-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462008#comment-13462008
]
Doug Cutting commented on AVRO-1170:
------------------------------------
Tests now pass for me with hadoop.version unspecified or with it set to 1 or 2.
It's unfortunate that we need three profiles. I now see that your previous
patch was just intended to work with either version unspecified or 2. That
might be preferable, as it removes redundancies in the pom that might later
result in problems. Regardless, we should probably add a comment describing
the possible values.
We should update the top-level build.sh so that it builds jars with both
classifiers. Also the release instructions will need updating so that we
publish both types to Maven.
Where should we document these classifiers for client applications?
Thanks for all your work on this, Tom!
> Avro's new mapreduce APIs don't work with Hadoop 2
> --------------------------------------------------
>
> Key: AVRO-1170
> URL: https://issues.apache.org/jira/browse/AVRO-1170
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.7.1
> Reporter: Tom White
> Assignee: Tom White
> Attachments: AVRO-1170.patch, AVRO-1170.patch, AVRO-1170.patch,
> AVRO-1170.patch
>
>
> Avro does not compile against Hadoop since some interfaces were changed to
> classes between Hadoop 1 and 2 (e.g. TaskAttemptContext).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
