-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
ClientID regex is too restrictive. #2697
Comments
@alexhein yes that's interesting, I have seen for example mirror connectors use I believe the original validation regex was based on the one that existed in the Java clients pre-1.0.0 but KIP-190 removed the client-side validation because instead the brokers were updated to be able to cope with any clientID and sanitize it before using it in metrics |
@dnwe Thank you for pointing me to the KIP, I was not aware of that. |
The original validation regex was based on the one that existed in the Java clients pre-1.0.0 but KIP-190 removed the client-side validation because instead the brokers were updated to be able to cope with any clientID and sanitize it before using it in metrics etc. We can do similar in Sarama and only do client-side validation when the user has specified a version number older than 1.0.0 Fixes #2697 Signed-off-by: Dominic Evans <[email protected]>
The original validation regex was based on the one that existed in the Java clients pre-1.0.0 but KIP-190 removed the client-side validation because instead the brokers were updated to be able to cope with any clientID and sanitize it before using it in metrics etc. We can do similar in Sarama and only do client-side validation when the user has specified a version number older than 1.0.0 Fixes #2697 Signed-off-by: Dominic Evans <[email protected]>
The original validation regex was based on the one that existed in the Java clients pre-1.0.0 but KIP-190 removed the client-side validation because instead the brokers were updated to be able to cope with any clientID and sanitize it before using it in metrics etc. We can do similar in Sarama and only do client-side validation when the user has specified a version number older than 1.0.0 Fixes #2697 Signed-off-by: Dominic Evans <[email protected]>
The original validation regex was based on the one that existed in the Java clients pre-1.0.0 but KIP-190 removed the client-side validation because instead the brokers were updated to be able to cope with any clientID and sanitize it before using it in metrics etc. We can do similar in Sarama and only do client-side validation when the user has specified a version number older than 1.0.0 Fixes #2697 Signed-off-by: Dominic Evans <[email protected]>
The original validation regex was based on the one that existed in the Java clients pre-1.0.0 but KIP-190 removed the client-side validation because instead the brokers were updated to be able to cope with any clientID and sanitize it before using it in metrics etc. We can do similar in Sarama and only do client-side validation when the user has specified a version number older than 1.0.0 Fixes #2697 Signed-off-by: Dominic Evans <[email protected]>
Description
The sarama client allows to set the client.id in the (producer) configuration. It is not uncommon to use symbols like '|' in the client ID string. The regex does not allow this, however. See
sarama/config.go
Line 18 in 82f0e48
The text was updated successfully, but these errors were encountered: