[
https://issues.apache.org/jira/browse/AVRO-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114920#comment-13114920
]
Doug Cutting commented on AVRO-895:
-----------------------------------
This is has been true since JSON input was first added in AVRO-50. Thiru
mentions it there in a comment (http://s.apache.org/E2N). Thiru, is it
possible to fix this in the resolver or parser? The field name is known before
it is parsed.
> JsonDecoder does not tolerate JSON records with different field order
> ---------------------------------------------------------------------
>
> Key: AVRO-895
> URL: https://issues.apache.org/jira/browse/AVRO-895
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Tom White
> Attachments: AVRO-895.patch
>
>
> Avro records are represented as JSON objects in the JSON encoding (according
> to the Avro spec http://avro.apache.org/docs/1.5.4/spec.html#schema_record).
> The JSON spec (http://www.json.org/) states that "A [JSON] object is an
> unordered set of name/value pairs". However, the Java JsonDecoder fails to
> read a JSON object as an Avro record if its fields are not in the same order
> as the schema.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
