You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2024/07/02 14:59:00 UTC

[jira] [Commented] (KAFKA-16255) AsyncKafkaConsumer should not use partition.assignment.strategy

    [ https://issues.apache.org/jira/browse/KAFKA-16255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862477#comment-17862477 ] 

Lianet Magrans commented on KAFKA-16255:
----------------------------------------

This is a duplicate of KAFKA-16786  which is already done. The follow-up would be adding a validation, tracked on KAFKA-16256, so closing this to clean up.  

> AsyncKafkaConsumer should not use partition.assignment.strategy
> ---------------------------------------------------------------
>
>                 Key: KAFKA-16255
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16255
>             Project: Kafka
>          Issue Type: Bug
>          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.9.0
>
>
> The {{partition.assignment.strategy}} configuration is used to specify a list of zero or more {{ConsumerPartitionAssignor}} instances. However, that interface is not applicable for the KIP-848-based protocol on top of which {{AsyncKafkaConsumer}} is built. Therefore, the use of {{ConsumerPartitionAssignor}} is inappropriate and should be removed from {{{}AsyncKafkaConsumer{}}}.



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