-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
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
Why are all the low-level (Java) Kafka AdminClient calls wrapped in effectBlocking
?
#492
Comments
guizmaii
changed the title
Why are all the low-level (Java) Kafka client calls wrapped in
Why are all the low-level (Java) Kafka AdminClient calls wrapped in May 12, 2023
effectBlocking
?effectBlocking
?
@guizmaii What shall we do with this one year old issue? |
@svroonland I'm still waiting for an answer/to understand why we need this and if we should keep these usages of blocking |
I suppose it was originally written that way as a precaution and probably after some actual experience of blocking in some circumstances. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AFAIK, and seeing that the Kafka AdminClient is using Java Futures (
KafkaFuture
implementingjava.util.concurrent.Future
and being based onCompletionStage
since Kafka 3.1 or 3.2), why are all the calls made with this client wrapped in aeffectBlocking
?Random example took from the code of zio-kafka:
The text was updated successfully, but these errors were encountered: