[
https://issues.apache.org/jira/browse/AVRO-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039936#comment-17039936
]
Zoltan Farkas commented on AVRO-2742:
-------------------------------------
[~rskraba] before I went the path of disabling name validation, I was thinking
of implementing something similar to percent encoding (use _ instead of %) to
basically convert arbitrary strings into ids...
disabling validation was the path of least resistance...
> Schema.Parser.parse() does not validate namespace
> -------------------------------------------------
>
> Key: AVRO-2742
> URL: https://issues.apache.org/jira/browse/AVRO-2742
> Project: Apache Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.9.2
> Reporter: radai rosenblatt
> Priority: Major
>
> [the spec|https://avro.apache.org/docs/current/spec.html#names] has the
> following to say about names:
> {quote}The name portion of a fullname, record field names, and enum symbols
> must: ... A namespace is a dot-separated sequence of such names.
> {quote}
> and yet the following schema parses just fine for me:
> {code:java}
> {
> "type": "record",
> "namespace": "this thing. has spaces.in it?!",
> "name": "HasInvalidNamespace",
> "fields": [
> {
> "name": "stringField",
> "type": "string"
> }
> ]
> }
> {code}
> am I misunderstanding the spec? also, even if this is technically a legal
> schema it will never survive code generation of specific record classes (at
> least in java?)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
