[
https://issues.apache.org/jira/browse/AVRO-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659943#comment-13659943
]
Scott Carey commented on AVRO-1315:
-----------------------------------
The issue is that the default value is different on different JVMs/compilers,
and that we break compatibility if there are any changes, even if they don't
have any effect -- such as adding an additional constructor. I felt that we
would be more likely to cause the default value to change than to make a change
that influenced serialization on such a trivial exception type.
Low risk no matter which way we go; I'd rather focus our energies elsewhere.
I'll remove it from the next patch.
> Java: Schema Validation utilities
> ---------------------------------
>
> Key: AVRO-1315
> URL: https://issues.apache.org/jira/browse/AVRO-1315
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Scott Carey
> Assignee: Scott Carey
> Fix For: 1.7.5
>
> Attachments: AVRO-1315.patch
>
>
> As part of AVRO-1124 we needed Schema Validation utilities. I have separated
> those out of that ticket as a stand-alone item.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
