[
https://issues.apache.org/jira/browse/AVRO-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715749#action_12715749
]
Arvind Jayaprakash commented on AVRO-36:
----------------------------------------
>From reading the existing spec, it is clear that schema type data is expected
>to be JSON compliant. However, it is not clear if Avro data is also expected
>to be a legitimate JSON fragment. The serialization scheme for all complex
>types has the potential to generate arbitrary byte streams.
As far as base64 v/s url encoding is concerned, base 64 routine implementations
across various programming languages are more portable than url encoding
routines. A classic example is PHP's urlencode converts spaces to + but
rawurlencode converts it to %20 whereas perl's routines believes that spaces
should always exist as %20.
Also, base64 has a consistent overhead (33%) whereas, url encoding can go
bonkers and bloat by 200% for around 75% of the byte values. So, if sending a
video clip (thus removing the probablity of most bytes being printable
US-ASCII), then url encoding will produce a significantly larger result than
base64.
> binary default values do not decode base64
> ------------------------------------------
>
> Key: AVRO-36
> URL: https://issues.apache.org/jira/browse/AVRO-36
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
>
> The specification says that default values for binary data are base64 encoded
> text, but the Java implementation uses the raw bytes of the textual value,
> and does not perform base64 decoded as specified.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
