[
https://issues.apache.org/jira/browse/AVRO-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724062#action_12724062
]
Sharad Agarwal commented on AVRO-62:
------------------------------------
The canonical form could be:
1. Off course no spaces, newlines. tabs etc
2. Type and message definitions in the same order as defined in the avpr file.
Types are defined using array, so those are already ordered. Messages are
defined in map, so parser have to retain the order.
If that is too much for some parsers, how about alphabetical ordering by
message names ?
> Canonicalize protocol string before computing MD5
> -------------------------------------------------
>
> Key: AVRO-62
> URL: https://issues.apache.org/jira/browse/AVRO-62
> Project: Avro
> Issue Type: Improvement
> Reporter: Sharad Agarwal
>
> Creating MD5 from non-canonical protocol string results in extra round trip
> and requires schema transfer over wire while doing inter language rpc. The
> protocol string should be canonicalized before computing MD5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.