You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2009/09/01 22:59:32 UTC
[jira] Updated: (AVRO-41) specific and generic instances should
implement comparable
[ https://issues.apache.org/jira/browse/AVRO-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated AVRO-41:
-----------------------------
Attachment: AVRO-41.patch
Here's a new version. Ordering is now always consistent with that of the binary comparator (AVRO-108). To do this required a few incompatible API changes:
- AVRO-110 (making GenericData and ReflectData into singletons)
- several methods moved from GenericDatumWriter to GenericData, so that they could be shared by the comparator code.
- adding a getSchema() method to GenericArray, so that it can implement compareTo().
Tests are added. Unless there are objections, I will commit this.
> specific and generic instances should implement comparable
> ----------------------------------------------------------
>
> Key: AVRO-41
> URL: https://issues.apache.org/jira/browse/AVRO-41
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Attachments: AVRO-41.patch, AVRO-41.patch
>
>
> Use of Avro instances with mapreduce would be simpler in many cases if they implemented Comparable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.