Use a proper Schema Registry client to fix issues in #22 #52
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.
In this PR, I've introduced a new dependency (https://github.com/riferrei/srclient) by @riferrei 馃檹 to fix issues reported in #22 (by @saad1200 and @ssam5532). By doing so, I've also refactored most of the code related to serdes functionality and created a few tickets along the way:
Breaking changes
I've broken backward compatibility with the schema registry client configuration object.
Issues
getSchema
function retrieves the latest version of the schema from Schema Registery, so I created an issue to make it optional by users@saad1200 and @ssam5532
I have tested it with
test_json.js
andtest_avro_with_schema_registry.js,
and I'd be happy to have your feedback.