You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Badai Aqrandista (JIRA)" <ji...@apache.org> on 2018/04/06 04:12:00 UTC
[jira] [Created] (KAFKA-6756) client.id and group.id validation in
the old vs new consumer
Badai Aqrandista created KAFKA-6756:
---------------------------------------
Summary: client.id and group.id validation in the old vs new consumer
Key: KAFKA-6756
URL: https://issues.apache.org/jira/browse/KAFKA-6756
Project: Kafka
Issue Type: Bug
Components: clients
Affects Versions: 1.1.0, 0.10.2.1
Reporter: Badai Aqrandista
It looks like the old consumer that is based on the Scala code validates "client.id" and "group.id" using this code:
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/common/Config.scala#L25]
[https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/consumer/ConsumerConfig.scala#L60]
However, the new consumer uses the Java code that does not validate "client.id" and "group.id" at all here:
[https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java#L264]
[https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerConfig.java#L298]
So the new consumer does not validate "client.id" and "group.id" like the old consumer. Either way, the documentation never specify the valid character for "client.id" and "group.id".
Is this a bug or by design?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)