[
https://issues.apache.org/jira/browse/AVRO-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702541#action_12702541
]
Doug Cutting commented on AVRO-17:
----------------------------------
I don't have a strong feeling here. It's in there now, and complicates Python
and Thrift compatibility a bit, but probably not so badly that we cannot deal
with the consequences if we think lots of folks will use this.
Note that, if we remove it, applications might use AVRO-10's fixed format to
store such 4-byte quantities.
For example, one could define something like:
{code}
{"name": "float", "type": "record", "fields": [{"name": "value", "type":
{"type": "fixed", "size": 4}}]}
{code}
We could even back-compatibly add things like this to a standard schema
library, automatically included in every schema, so that applications could
refer to these again as just "float", and runtimes could include optimized
handling of such types. Double, md5, datetime, etc. might all be implemented
this way.
Hmm. If we intend to go this way, then perhaps removing it now isn't required,
since we can back-compatibly re-define it with a standard library...
> remove single float type
> ------------------------
>
> Key: AVRO-17
> URL: https://issues.apache.org/jira/browse/AVRO-17
> Project: Avro
> Issue Type: Improvement
> Components: spec
> Reporter: Doug Cutting
> Fix For: 1.0
>
>
> Python and Thrift do not support a 32-bit single float type, nor do many
> applications use this type, so, for better compatibility, we can remove it
> from Avro.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
