[
https://issues.apache.org/jira/browse/AVRO-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903757#action_12903757
]
Scott Carey commented on AVRO-637:
----------------------------------
bq. If it is #2, I feel that Iterable is a better generalization for an Avro
array than Collection.
Well, now that I think about it a bit more, there is the (very big) problem of
size() not existing on Iterable. So I'll correct myself and say that
Collection is as high up the inheritance tree we can go. if #2 is the goal.
> 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, 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.
