[
https://issues.apache.org/jira/browse/AVRO-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751786#comment-13751786
]
Doug Cutting commented on AVRO-1368:
------------------------------------
> Perhaps, the stringable concept should be moved to GenericData instead?
Perhaps, but that would be much more incompatible. Adding stringables to
specific permitted some things to work (e.g., BigInteger) that used to fail,
which is not 100% compatible, but largely. With generic, it would cause
schemas that were readable before to change the representation they're read
into. So such a change, if desired, would need to go into 1.8.0.
Is this desired? With generic, any schema can be read into a closed set of
classes. With extensible stringables this would no longer be true. That makes
it harder to write programs that can generically process data of any schema.
> is there a reason for Avro integer to accept any Java Number, and silently
> convert/truncate them to Integer, while other Avro primitive types will
> require an exact class match (eg. Avro long will require Java Long, and not
> accept Java Integer).
In reflect, an int schema is used to handle Java's Byte, Character and Short
types too. Is that what you're referring to?
> String schema accepts any Java object, and converts it with toString()
> ----------------------------------------------------------------------
>
> Key: AVRO-1368
> URL: https://issues.apache.org/jira/browse/AVRO-1368
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.7.5
> Reporter: Christophe Taton
>
--
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
