[KAFKA-15773] Group protocol configuration should be validated

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.9.0
• Component/s: clients, config, consumer
• Labels: kip-848-client-support
• Assignee: PoAn Yang
• Reporter: Philip Nee
• Created: 02/Nov/23 15:48
• Updated: 13/Aug/24 21:02
• Resolved: 18/Jul/24 10:31

Description

If the user specifies using the generic group, or not specifying the group.protocol config at all, we should invalidate all group.remote.assignor

 

If group.local.assignor and group.remote.assignor are both configured, we should also invalidate the configuration

 

This is an optimization/user experience improvement.

Issue Links

• fixes: KAFKA-16256 Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
• is related to: KAFKA-16255 AsyncKafkaConsumer should not use partition.assignment.strategy
• is related to: KAFKA-16256 Update ConsumerConfig to validate use of group.remote.assignor and partition.assignment.strategy based on group.protocol
• relates to: KAFKA-17338 ConsumerConfig should prevent using partition assignors with CONSUMER group protocol
• links to: GitHub Pull Request #16543