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

Make sasl.Mechanism safe for concurrent use #323

Merged
merged 1 commit into from
Jul 24, 2019
Merged

Conversation

stevevls
Copy link
Contributor

While is a breaking change for the sasl.Mechanism interface, it's
not expected that library clients are implementing said interface
as Kafka only accepts a very specific set of mechanisms.

Fixes #317

While is a breaking change for the sasl.Mechanism interface, it's
not expected that library clients are implementing said interface
as Kafka only accepts a very specific set of mechanisms.

Fixes #317
@stevevls stevevls requested a review from achille-roussel July 23, 2019 23:30
@stevevls
Copy link
Contributor Author

@achille-roussel I think we can make a case here for ignoring b/w compatibility similar to the way that we did with the streaming compression change, but LMK if you think otherwise.

Copy link
Contributor

@achille-roussel achille-roussel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good 👍

@stevevls stevevls merged commit 3d2413f into master Jul 24, 2019
@stevevls stevevls deleted the fix-concurrent-sasl branch July 24, 2019 15:25
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

Successfully merging this pull request may close these issues.

Reading message fails with SASL_SSL when using consumer groups
2 participants