You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2024/03/11 17:00:00 UTC

[jira] [Updated] (KAFKA-16256) Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol

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

Kirk True updated KAFKA-16256:
------------------------------
    Priority: Minor  (was: Major)

> Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-16256
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16256
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, consumer
>    Affects Versions: 3.7.0
>            Reporter: Kirk True
>            Assignee: Kirk True
>            Priority: Minor
>              Labels: consumer-threading-refactor, kip-848-client-support
>             Fix For: 3.8.0
>
>
> {{ConsumerConfig}} supports both the {{group.remote.assignor}} and {{partition.assignment.strategy}} configuration options. These, however, should not be used together; the former is applicable only when the {{group.protocol}} is set to {{consumer}} and the latter when the {{group.protocol}} is set to {{{}classic{}}}. We should emit a warning if the user specifies the incorrect configuration based on the value of {{{}group.protocol{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)