[AVRO-1836] avro schema compatibility checking does not work for records.

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Not A Problem
• Affects Version/s: 1.8.0
• Assignee: Unassigned
• Reporter: Yan Cui
• Created: 27/Apr/16 18:18
• Updated: 02/May/16 18:03
• Resolved: 02/May/16 15:38

Description

Hi Guys,

We found a problem on avro 1.8.0 when calling avro's compatibility checking.
Specifically, we used the function checkReaderWriterCompatibility,
it works with no problem when we provides simple schema, like oldschema=

{"type":"int"}

schema=

{"type":"long"}

, but when we use complicated schema, like
oldschema={"type":"record","name":"twitter","fields":[

{"name":"username","type":"string"}

]}

schema={"type":"record","name":"twitter","fields":[

{"name":"username","type":"string"}

]}

it reports that record name(twitter in this case) cannot be redefined.
When one rename the second schema, it told me the two schema are not compatible. Actually, for the completed case, oldschema and schema are exactly the same, the output is expected to be compatible.

Do you guys have any ideas about this?

Thanks, Yan