Avro Reader and Writer Compatibility

• Enter values using the examples, or choose a local file where requested. Follow the displayed supported input shapes and limits.
• Choose Calculate result and inspect the complete result.
• Download result to save the primary file. Where supplied, additional links save source files and the full JSON report. Reset restores examples and clears output.

Writer schema JSON: {
"type": "record",
"name": "Person",
"fields": [
{
"name": "name",
"type": "string"
}
]
}
Reader schema JSON: {
"type": "record",
"name": "Person",
"fields": [
{
"name": "name",
"type": "string"
},
{
"name": "age",
"type": "int",
"default": 0
}
]
}

• Avro1.12 declared resolution:unqualified named-type matching and reader full/relative aliases,reader field names/aliases/defaults,numeric widening,string/bytes promotion,arrays/maps/unions/enums/fixed. Check every possible writer branch and resolve the first matching reader branch. Missing reader fields need their own field default;enum fallbacks cover missing symbols only. Reuse exact structural/default validation;refuse any uninterpreted logicalType annotation or ambiguous field-alias mapping. Supported incompatibility gives a negative report with reader data paths and writerUnion markers;recursive active pairs terminate and finite default paths describe possible use,not decoded data. At most100000 pair/lookup checks,80 expanded pair levels,2000 issues/default paths. No data encoding,generated code,complete logical/schema equivalence or runtime interoperability guarantee.
• Text fields are limited to100,000 UTF16 units each and400,000 combined UTF8 bytes; file fields have their own displayed limits. Combined output is at most4MiB. Processing stops after30 seconds; tool-specific bounds may be tighter.
• Generated source is a downloadable result and is not executed here. Inspection does not establish remote behavior, trust or standards certification.