KAFKA-10713: (redux) Also allow underscore in protocol name#9701
KAFKA-10713: (redux) Also allow underscore in protocol name#9701tombentley wants to merge 1 commit intoapache:trunkfrom
Conversation
|
I don't think it's enough. The
But clients also accept So if a protocol is specified, we should allow any characters. |
|
OK, but then we either:
It seems that the protocol was first added in 53f3143 (part of https://cwiki.apache.org/confluence/display/KAFKA/Multiple+Listeners+for+Kafka+Brokers), but it's not really clear why it was allowed for client configs. While option 2 is easiest, I feel that 3 is closer to the right thing to do: Having documentation and implementation aligned will prevent other possible errors people might make, especially as this code is slowly being reused for other configs. Thoughts? |
|
Perhaps we should have a KIP and discussion for this since it changes existing public behavior? In the meantime, we should probably revert the original PR. |
|
If we want to make a change that is not backwards compatible, it would be best to do it in 3.0. Either way, a KIP is needed and it makes sense to revert/adjust so that compatibility is preserved for now. |
|
@tombentley Done. |
|
Thanks @ijuma, I've opened https://cwiki.apache.org/confluence/display/KAFKA/KIP-697%3A+Stricter+parsing+of+addresses+in+configs, targetting 3.0. |
No description provided.