[AVRO-2838] Schema in generated Java class is different than the original one

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: java
• Assignee: Unassigned
• Reporter: Lukas Krecan
• Created: 15/May/20 17:08
• Updated: 27/Sep/21 06:28

Description

If you generate Java classes from schema, SCHEMA$ variable differs from the original schema. It causes issues like this and this when using Schema registry.

The issue happens when the schema in the registry is configured externally and then you try to use generated Java class. The schema in the registry does not match the schema in the class and thus the write is refused.

Technically it's easy to fix (see the attached patch) but I guess there will be some backward compatibility concerns.

If it is not acceptable, would it be at least possible to add the originalSchema context variable so we could solve it using custom template.

The patch is not final, its purpose is just to convey the idea.

Issue Links

• relates to: AVRO-3217 Avro IDL does not allow creation of avro.java.string subtype
• relates to: AVRO-3077 Ability of select string deserializing mode by configuration
• relates to: AVRO-803 Java generated Avro classes make using Avro painful and surprising