[
https://issues.apache.org/jira/browse/AVRO-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786230#action_12786230
]
Philip Zeyliger commented on AVRO-249:
--------------------------------------
bq. Floats aren't encoded varint, are they? I can't see the advantage there,
the high bits will be set too frequently.
Yes, they're not encoded varint. Totally bogus statement on my part.
bq. [Thoughts on a unified API]
Scott, I totally see where you're going. I think an "annotation-based" API
would be a great addition. Even though it's possible to unify "specific" and
"reflection" APIs under that one roof, I really like the simplicity of the
"specific" API. This comes in part from some experience with Protocol Buffers.
Yes, it sucks to wrap each of your data classes with another class, but, in
practice, this is often easier to follow than stuff that does some magic behind
your back.
In terms of examples, ORMs solve the same sorts of problems. Hiberate and
friends deserve a look too, though I agree Jackson is more similar.
> in reflection, represent Java short as fixed data
> -------------------------------------------------
>
> Key: AVRO-249
> URL: https://issues.apache.org/jira/browse/AVRO-249
> Project: Avro
> Issue Type: Improvement
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.3.0
>
> Attachments: AVRO-249.patch, AVRO-249.patch, AVRO-249.patch
>
>
> Currently the Java reflect API treats shorts as ints. This fails however to
> naturally handle shorts in arrays and other containers. It would be better
> if we used a distinct type for reflected Java short values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.