[
https://issues.apache.org/jira/browse/AVRO-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720968#action_12720968
]
Doug Cutting commented on AVRO-50:
----------------------------------
> [type, value] for unions breaks down if you have a fixed2 unioned with a
> fixed4.
In the case of fixed (and records) we use the defined name of the type. E.g. a
value of type {"type": "fixed", "name": "MD5", "size": 16} could, if in a
union, have a JSON value like ["MD5", "0123456789abcdef"].
Note also that, except for records and fixed, unions are not permitted to
contain multiple entries of the same type
((http://hadoop.apache.org/avro/docs/current/spec.html#Unions).
> bidrectional text representation of AVRO data
> ---------------------------------------------
>
> Key: AVRO-50
> URL: https://issues.apache.org/jira/browse/AVRO-50
> Project: Avro
> Issue Type: New Feature
> Components: spec
> Reporter: Philip Zeyliger
>
> It would be very useful to add a text representation of AVRO data to the
> spec, and implement toString() and fromString() in all implementations.
> Faced with binary data, it'll be a useful operation to decode it for
> debugging, ad-hoc manipulation, etc.
> I suspect the text format will:
> * be JSON
> * require the schema for full interpretation
> * map easily onto the binary format (if the binary format has a signifier to
> take a specific branch of a union, the text format will have such a signifier
> as well)
> * not be unique (there's more than one way to encode a given number (e.g.,
> {{0x0 == 0}}) or string (e.g., {{"\u0061" == "a"}}, not to mention flexible
> whitespace)
> * be compatible, for the binary type, with whatever is decided in AVRO-36
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.