[
https://issues.apache.org/jira/browse/AVRO-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978949#comment-16978949
]
ASF subversion and git services commented on AVRO-621:
------------------------------------------------------
Commit f8afef1f98b1f27deb9e73ef804ed74ba2d20bbb in avro's branch
refs/heads/master from Michael A. Smith
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=f8afef1 ]
AVRO-621: Stricter Name Validation (#718)
* AVRO-621: Test an Invalid Name
* AVRO-621: Stricter Name Checking
* AVRO-621 Adhere Better to Spec
* AVRO-621 More Complete Name Tests
> Python library allows for incorrect field names in schema validation
> --------------------------------------------------------------------
>
> Key: AVRO-621
> URL: https://issues.apache.org/jira/browse/AVRO-621
> Project: Apache Avro
> Issue Type: Improvement
> Components: python
> Affects Versions: 1.3.3
> Reporter: Gavin M. Roy
> Assignee: Michael A. Smith
> Priority: Major
>
> When using the schema.parse() function, you can pass in fields with the name
> parameter violating the [A-Za-z_] specified for field names. As the c
> library (and others I assume) strictly check for this, it is possible to
> create a scenario where the schema is incompatible across languages.
> For example, one can make a field: {"name": "15_miles", "type": "null"} which
> would be invalid elsewhere due to the name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
