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

• Type: Improvement
• Status: Resolved
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: 3.7.0
• Fix Version/s: 3.9.0
• Component/s: clients, config, consumer
• Labels: consumer-threading-refactor kip-848-client-support
• Assignee: Kirk True
• Reporter: Kirk True
• Created: 14/Feb/24 17:28
• Updated: 09/Aug/24 19:28
• Resolved: 09/Aug/24 19:28

Description

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.

Issue Links

• is fixed by: KAFKA-15773 Group protocol configuration should be validated
• is related to: KAFKA-16255 AsyncKafkaConsumer should not use partition.assignment.strategy
• relates to: KAFKA-15773 Group protocol configuration should be validated