[
https://issues.apache.org/jira/browse/AVRO-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756906#comment-13756906
]
Christophe Taton commented on AVRO-1368:
----------------------------------------
Doug, I realize my reply to you last question didn't go through.
Very personally, I dislikes silent, implicit conversions, and especially lossy
ones.
If we had the choice, I would rather narrow these to only handle Integer, Short
and Character.
As you mention, this would be an incompatible API change. Is it eligible for
the coming 1.8?
That said, accepting an Integer where a long is expected would make sense.
Similarly, accepting a Float where a double is expected would make sense too.
I believe both could be implemented now in a compatible way.
The question that remains is about performance.
> 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
> Attachments: AVRO-1368.20130828-160759.patch
>
>
--
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
