[
https://issues.apache.org/jira/browse/AVRO-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated AVRO-1170:
----------------------------
Attachment: AVRO-1170.patch
Here's a new patch with just two profiles. I've added a comment to the
top-level Java POM explaining the usage.
bq. 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.
I updated the top-level build.sh to build both JARs. I'm not sure exactly how
the release instructions change (see earlier comment), but it should be
possible to figure that out at release time. We might need to put a note in
them as a reminder.
bq. Where should we document these classifiers for client applications?
How about adding a question to the FAQ? It would look a bit like last part of
https://issues.apache.org/jira/browse/AVRO-1170?focusedCommentId=13459646&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13459646.
I can add that once a release is made.
> 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-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
