You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Oscar Westra van Holthe - Kind (Jira)" <ji...@apache.org> on 2022/05/16 18:43:00 UTC
[jira] [Comment Edited] (AVRO-3374) [Java] Fully qualified type reference "ns.int" loses namespace.
[ https://issues.apache.org/jira/browse/AVRO-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537719#comment-17537719 ]
Oscar Westra van Holthe - Kind edited comment on AVRO-3374 at 5/16/22 6:42 PM:
-------------------------------------------------------------------------------
What is correct?
The spec says: "Primitive type names have no namespace and their names may not be defined in any namespace"
Should we change the spec and allow primitive names if defined in a namespace? Or stick to the spec and disallow primitive names in any namespace?
was (Author: opwvhk):
What is correct?
The spec says: "Primitive type names have no namespace and their names may not be defined in any namespace"
Should we change the spec and allow primitive names if defined in a namespace? Or atypical to the spec and disallow primitive names in any namespace?
> [Java] Fully qualified type reference "ns.int" loses namespace.
> ---------------------------------------------------------------
>
> Key: AVRO-3374
> URL: https://issues.apache.org/jira/browse/AVRO-3374
> Project: Apache Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.11.0
> Reporter: Ryan Skraba
> Assignee: Christophe Le Saec
> Priority: Minor
>
> While brainstorming for AVRO-3370, I came across this special case where a type-reference could be considered ambiguous if the SDK is not careful when simplifying inherited namespaces:
> {code:json}
> {
> "type" : "record",
> "name" : "ns.int",
> "fields" : [
> {"name" : "value", "type" : "int"},
> {"name" : "next", "type" : [ "null", "ns.int" ]}
> ]
> }
> {code}
> In Java, if this code is parsed, it works as expected (as a linked list).
> If the schema is turned to a String using toString(), the namespace is dropped off the last {*}{{ns.int}}{*}, turning it into the primitive. That string can still be parsed into a Schema, but the "round-trip" modifies the schema in an incompatible way.
> That namespace shouldn't be dropped when producing the JSON string representing the Schema in Java.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)