[
https://issues.apache.org/jira/browse/FLINK-32893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766948#comment-17766948
]
Mason Chen commented on FLINK-32893:
------------------------------------
We discussed this offline. It is unclear whether or not this is actually
required since Kafka quotas seem to be able to use an opaque principal name as
per [https://docs.confluent.io/kafka/design/quotas.html]. The client.id
parameter is optional from the Kafka perspective and I'm not sure we should
violate this.
In addition, it doesn't make sense to use quotas without proper auth and proper
auth as noted in the docs should be able to identify a client without the
`client.id` parameter.
I would opt to mark this ticket as "not a problem" unless there are differing
opinions
> Make client.id configurable from KafkaSource
> --------------------------------------------
>
> Key: FLINK-32893
> URL: https://issues.apache.org/jira/browse/FLINK-32893
> Project: Flink
> Issue Type: Improvement
> Affects Versions: 1.17.1
> Reporter: Mason Chen
> Priority: Major
> Labels: pull-request-available
>
> The client id is not strictly configurable from the KafkaSource because it
> appends a configurable prefix and subtask information to avoid the mbean
> conflict exception messages that are internal to the Kafka client.
>
> However, various users reported that they need use this client.id for Kafka
> quotas and they need to have control over the client.id to enforce quotas
> properly.
>
> Affects Kafka connector 3.1 and below.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
