[
https://issues.apache.org/jira/browse/AVRO-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230165#comment-14230165
]
Ryan Blue commented on AVRO-1613:
---------------------------------
Is there an extension to the JSON specification that allows these? I'd rather
not rely on a single library's behavior because the schema needs to be usable
across all of the different language implementations. That complicates rolling
out a feature like this because we would be introducing an incompatibility
while Java can read a schema that appears invalid in, say, Python. If there is
a specification for these that we can migrate to, then I think this is possible.
Also, is the motivation for this something that is addressed by
[IDL|https://avro.apache.org/docs/1.7.5/idl.html]? It seems like the motivation
here is to make it easier to write schemas by hand, but I think the JSON
representation isn't necessarily the best place to do that.
> 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)
