[KAFKA-16786] New consumer should not require the deprecated partition.assignment.strategy

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.8.0
• Component/s: clients, consumer
• Labels: kip-848-client-support
• Assignee: Lianet Magrans
• Reporter: Lianet Magrans
• Reviewer: Lucas Brutschy
• Created: 16/May/24 14:36
• Updated: 07/Jun/24 07:31
• Resolved: 06/Jun/24 13:21

Description

The partition.assignment.strategy config is deprecated with the new consumer group protocol KIP-848. With the new protocol, server side assignors are supported for now, defined in the property
group.remote.assignor, and with default values selected by the broker, so it's not even a required property.

The new AsyncKafkaConsumer supports the new protocol only, but it currently throws an IllegalStateException if a call to subscribe is made and the deprecated config partition.assignment.strategy is empty (see throwIfNoAssignorsConfigured).
 
We should remove the reference to ConsumerPartitionAssignor in the AsyncKafkaConsumer, along with it's validation for non-empty on subscribe (only use it has)

Issue Links

• duplicates: KAFKA-16255 AsyncKafkaConsumer should not use partition.assignment.strategy
• links to: GitHub Pull Request #16214