We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SchemaRegistryClient is based on requests, which is basically sync. Therefore it is not suitable for async applications.
SchemaRegistryClient
I suggest to implement AsyncSchemaRegistryClient based on aiohttp.
AsyncSchemaRegistryClient
The text was updated successfully, but these errors were encountered:
Actually we do not need this anymore.
We've implemented our own SchemaRegistryClient based on fastavro and httpx, which just calls REST endpoints.
It was pretty easy, I would recommend anyone doing the same, if you want absolute flexibility.
Sorry, something went wrong.
No branches or pull requests
Description
SchemaRegistryClient
is based on requests, which is basically sync. Therefore it is not suitable for async applications.I suggest to implement
AsyncSchemaRegistryClient
based on aiohttp.The text was updated successfully, but these errors were encountered: