Skip to content

Fix #812: fall back when an Avro type id is not a class - #813

Open
adityabagla7 wants to merge 1 commit into
FasterXML:3.xfrom
adityabagla7:fix-812-avro-missing-type
Open

adityabagla7 wants to merge 1 commit into
FasterXML:3.xfrom
adityabagla7:fix-812-avro-missing-type

Conversation

@adityabagla7

Copy link
Copy Markdown

On 3.x, reading Avro as Object failed when the record name was not a Java class. 2.x used the base type instead, so the result was a Map.

This only falls back for "no such class found". Illegal subtype and validator errors still throw.

The failing test is moved to interop/records/RecordWithMissingTypeTest and the expected-failure mark is removed. RecordWith*Test passed locally.

Made with Cursor

A missing record name should read as the base type again, so Object
becomes a Map. Illegal subtype errors still throw.

Co-authored-by: Cursor <cursoragent@cursor.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant