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 2010/08/28 01:41:53 UTC

[jira] Updated: (AVRO-637) GenericArray should implement Collection

     [ https://issues.apache.org/jira/browse/AVRO-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting updated AVRO-637:
------------------------------

    Attachment: AVRO-637.patch

Here's a patch for this.  This changes GenericArray<T> to implement List<T>.  It also changes specific and generic to accept arbitrary Collection implementations as array parameters and field values.

This change is incompatible, in that it changes generated method signatures and field types.  If someone approves it today, then I can commit it and quickly roll another 1.4.0 candidate, otherwise it might have to wait until 1.5.0.

> GenericArray should implement Collection
> ----------------------------------------
>
>                 Key: AVRO-637
>                 URL: https://issues.apache.org/jira/browse/AVRO-637
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.5.0
>
>         Attachments: AVRO-637.patch
>
>
> It would be nice if Avro arrays were better integrated with Java collections.  The GenericArray interface permits array element reuse, which is awkward with java.util.Collection.  But if GenericArray implemented Collection and the Avro runtime permitted arbitrary Collection implementations to be passed for Arrays then it would simplify many applications.  The runtime could still reuse elements if an array implemented GenericArray, so performance would not suffer for applications that, e.g., loop over a data file, reusing instances.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.