[AVRO-3374] [Java] Fully qualified type reference "ns.int" loses namespace.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.11.0
• Fix Version/s: 1.11.1
• Component/s: java
• Labels: pull-request-available pull-requests-available
• Assignee: Christophe Le Saec
• Reporter: Ryan Skraba
• Created: 07/Feb/22 17:43
• Updated: 24/Jun/22 15:14
• Resolved: 24/Jun/22 15:14

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.

Issue Links

• links to: GitHub Pull Request #1688