[
https://issues.apache.org/jira/browse/AVRO-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725282#action_12725282
]
Doug Cutting commented on AVRO-50:
----------------------------------
I spoke with Raymie about this, and he suggested that the parser-based schema
handling logic in AVRO-29 might be instead used to insert record boundaries,
field names, etc. So one might instead add these methods only to a
parser-based encoder/decoder subclasses rather than to the base classes, so
that applications that read and write data need not explicitly invoke them.
> 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
> Assignee: Doug Cutting
> Attachments: AVRO-50.patch
>
>
> 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.