Skip to content
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

Is ssl.ca.location correctly checked? #188

Closed
Gau-thier opened this issue Oct 27, 2021 · 2 comments
Closed

Is ssl.ca.location correctly checked? #188

Gau-thier opened this issue Oct 27, 2021 · 2 comments

Comments

@Gau-thier
Copy link
Contributor

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 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

@AlexeyRaga
Copy link
Member

AlexeyRaga commented Oct 27, 2021

Hi, I will have a look, but I don't remember that hw-kafka-client even knows about or has anything to do with ssl.ca.location.

I feel like there is something weird about the use of ssl.ca.location property.

How do you set this property?

@Gau-thier
Copy link
Contributor Author

Hi @AlexeyRaga!

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:
image

Sorry to have bothered you about that 🙏🏻, hw-kafka-client is totally out of concern of this trouble!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants