You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Yanwen Lin (Jira)" <ji...@apache.org> on 2021/09/08 03:58:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17411669#comment-17411669 ]
Yanwen Lin commented on KAFKA-10038:
------------------------------------
Hey [~guozhang], per this wiki: [https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes#ContributingCodeChanges-PullRequest], when a PR is merged, the related Jira ticket will also be closed automatically.
The PR in this ticket is linked and is already merged (PR: [https://github.com/apache/kafka/pull/11297]), but this ticket status is still PATCH AVAILABLE? Is there anything I missed? Or should I close this ticket manually? Thanks!
> 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: Yanwen Lin
> Priority: Minor
> Labels: newbie, performance
>
> 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)