You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2010/02/01 18:52:18 UTC
[jira] Commented: (AVRO-261) Allow Schemas to be immutable
[ https://issues.apache.org/jira/browse/AVRO-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828198#action_12828198 ]
Philip Zeyliger commented on AVRO-261:
--------------------------------------
I like having schemas immutable. This patch looks like a good step in that direction. setProp() is still problematic, however. (It's also the reason that the primitive schemas aren't singletons: I think the reflect API annotates the primitive types with stuff.) I also wish that we could just get rid of setFields() altogether, relying on the constructor.
> 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
>
>
> 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.