You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Randall Hauch (Jira)" <ji...@apache.org> on 2020/06/24 20:52:00 UTC

[jira] [Updated] (KAFKA-10038) ConsumerPerformance.scala supports the setting of client.id

     [ https://issues.apache.org/jira/browse/KAFKA-10038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated KAFKA-10038:
----------------------------------
    Fix Version/s:     (was: 2.6.0)
                   2.7.0

Since this is not a blocker issue, as part of the 2.6.0 release process I'm changing the fix version to `2.7.0`. If this is incorrect, please respond and discuss on the "[DISCUSS] Apache Kafka 2.6.0 release" discussion mailing list thread.

> ConsumerPerformance.scala supports the setting of client.id
> -----------------------------------------------------------
>
>                 Key: KAFKA-10038
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10038
>             Project: Kafka
>          Issue Type: Improvement
>          Components: consumer, core
>    Affects Versions: 2.1.1
>         Environment: Trunk branch
>            Reporter: tigertan
>            Assignee: Luke Chen
>            Priority: Minor
>              Labels: newbie, performance
>             Fix For: 2.7.0
>
>
> ConsumerPerformance.scala supports the setting of "client.id", which is a reasonable requirement, and the way "console consumer" and "console producer" handle "client.id" can be unified. "client.id" defaults to "perf-consumer-client".
> We often use client.id in quotas, if the script of kafka-producer-perf-test.sh supports the setting of "client.id" , we can do quota testing through scripts without writing our own consumer programs. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)