[
https://issues.apache.org/jira/browse/AVRO-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831058#action_12831058
]
Doug Cutting commented on AVRO-261:
-----------------------------------
The List-based fields interface is indeed an improvement, since iterating over
maps is awkard in Java. +1 for that.
One nit: I prefer the name LockableList to LockableArrayList. Otherwise I'm
okay with this patch.
An standalone List implementation might be more clearly immutable than one
based on ArrayList. But the Google collections jar is over 500k, which would
make, e.g., the tools jar that much bigger. Copying just the ImmutableList
code into this project could be a little tricky, since its not a single,
standalone file. Philip, do you want to construct a patch that copies the
minimal code from Google, building a standalone ImmutableList that's not based
on ArrayList?
> Allow Schemas to be immutable
> -----------------------------
>
> Key: AVRO-261
> URL: https://issues.apache.org/jira/browse/AVRO-261
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Kevin Oliver
> Assignee: Thiruvalluvan M. G.
> Priority: Minor
> Attachments: AVRO-261.patch, AVRO-261.patch, AVRO-261.patch
>
>
> It would be nice if there was the ability to have an immutable Schema in
> java.
> Without this, it makes sharing schemas risky. Also, with this, we could
> (lazily) cache the hashCode which is a fairly expensive operation today,
> especially on something like a record.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
