Make reader schema optional in AvroDeserializer #1000
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was created in response to the following issue:
#834
It makes the reader schema optional in
AvroDeserializer
. When it is not provided, the writer schema is used for deserialization. Tests were updated to verify the deserializer works both with and without a reader schema.NOTE: this PR introduces breaking changes in both the
AvroSerializer
andAvroDeserializer
. The order of constructor arguments forAvroDeserializer
had to changed to accommodate the now optionalschema_str
argument. I reordered the constructor arguments forAvroSerializer
just for consistency between the two classes.