[
https://issues.apache.org/jira/browse/AVRO-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223419#comment-13223419
]
Doug Cutting commented on AVRO-1022:
------------------------------------
Raymie, this is a good approach. The spec language that requires ASCII should
be changed from MUST to SHOULD.
One use case that Scott mentioned that your prose does not is transmitting
schemas from other systems, e.g., Avro Schemas might often be generated
automatically from Pig or SQL schemas. In these cases accepting liberally
permits schemas to pass through Avro losslessly. Strict validation is really
only useful when a developer is the schema author. In many (most?) cases Avro
might be an underlying tool, used indirectly through an application, and in
these cases strict validation is probably not useful.
> Error in validate name
> ----------------------
>
> Key: AVRO-1022
> URL: https://issues.apache.org/jira/browse/AVRO-1022
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Raymie Stata
> Priority: Minor
> Attachments: AVRO-1022.patch, AVRO-1022.patch,
> unicode-recommendation.html
>
>
> Fix schema.validateName to allow only ASCII letters, not Unicode letters.
--
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