You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Everything is in the title 😅.
I firstly created the issue #182, but it turns out it is not linked to the rdkafka version used into hw-kafka-client.
I feel like there is something weird about the use of ssl.ca.location property. This trouble appears while we tried to update to your latest version. Hence, the problem seems to come from your library.
Would you mind help us to solve this? In our case, the ssl.ca.location is mandatory, and we cannot reach the consumed Kafka without it.
Best regards,
Gauthier
The text was updated successfully, but these errors were encountered:
I finally got the answer!
The rdkafka I am provisioning with my nix-shell (on nixpkgs-unstable) is the 1.8.0, while the latest (installed globally from brew install librdkafka) is the 1.8.2.
A quick look at the release notes, just confirm my thoughts:
Sorry to have bothered you about that 🙏🏻, hw-kafka-client is totally out of concern of this trouble!
Hello,
Everything is in the title 😅.
I firstly created the issue #182, but it turns out it is not linked to the
rdkafka
version used intohw-kafka-client
.I feel like there is something weird about the use of
ssl.ca.location
property. This trouble appears while we tried to update to your latest version. Hence, the problem seems to come from your library.Would you mind help us to solve this? In our case, the
ssl.ca.location
is mandatory, and we cannot reach the consumed Kafka without it.Best regards,
Gauthier
The text was updated successfully, but these errors were encountered: