avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AVRO-36) binary default values do not decode base64
Date Wed, 03 Jun 2009 00:06:09 GMT

    [ https://issues.apache.org/jira/browse/AVRO-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715758#action_12715758
] 

Doug Cutting commented on AVRO-36:
----------------------------------

> However, it is not clear if Avro data is also expected to be a legitimate JSON fragment.

No.  The only concern here is the encoding within JSON of the default value for binary field.

> base 64 routine implementations across various programming languages are more portable
than url encoding routines

Although different url encoders may provide different encodings, won't they all decode to
the same byte string?  The specification permits space to be encoded in multiple ways, but
either a + or a %20 must decode to 32, no?  So, unless I'm missing something, I don't see
this as a problem.

> if sending a video clip ...

I would not expect something as large as a video clip as the default value in a schema for
a binary field.


> 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.


Mime
View raw message