Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.11.0
Description
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:
{ "type" : "record", "name" : "ns.int", "fields" : [ {"name" : "value", "type" : "int"}, {"name" : "next", "type" : [ "null", "ns.int" ]} ] }
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.
Attachments
Attachments
Issue Links
- links to