[
https://issues.apache.org/jira/browse/AVRO-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118182#comment-13118182
]
Thiruvalluvan M. G. commented on AVRO-895:
------------------------------------------
JsonParser2 is actually a narrower version of Jackson's JsonParser. Actually
there is no need for that interface. I use it just to avoid implementing all
the methods of JsonParser for the saved tokens. Now looking back, it doesn't
seem to be worth it. It forces us to have an adaptor to adapt JsonParser into
JsonParser2, which appears wasteful.I'll get rid of that JsonParser2 altogether.
I have no issues with removing the underscores in test names.
> 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
> Affects Versions: 1.5.4
> Reporter: Tom White
> Assignee: Thiruvalluvan M. G.
> Labels: patch
> Fix For: 1.6.0
>
> Attachments: AVRO-895.patch, 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
