[
https://issues.apache.org/jira/browse/AVRO-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233300#comment-14233300
]
Doug Cutting commented on AVRO-1613:
------------------------------------
By Postel's Law we might be liberal in the JSON syntax we accept, but we should
always produce JSON that adheres closely to the standard. There is a risk that
another implementation may not be able to read a .avsc file that uses
non-standard syntax, but data files, protocol handshakes, schema repositories
etc. should always use standard syntax and thus no interoperability problems
are created there. So the question is whether folks use a given .avsc file
with multiple Avro implementations.
We do currently allow comments. Unquoted field names would make it easier to
both type-in and read hand-written schemas. I don't see significant value in
supporting single quotes.
> Support for non-standard JSON when reading schemas
> --------------------------------------------------
>
> Key: AVRO-1613
> URL: https://issues.apache.org/jira/browse/AVRO-1613
> Project: Avro
> Issue Type: Wish
> Components: java
> Reporter: Alfonso Nishikawa
> Priority: Minor
>
> It would be good to:
> * Allow unquoted field names
> * Allow single quotes
> * Allow comments
> when reading a schema. The proper extensions ([shown
> here|http://wiki.fasterxml.com/JacksonFeaturesNonStandard]) of Jackson could
> be enabled in {{Schema$Parser.parse(JsonParser)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
