You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Allen Wang (JIRA)" <ji...@apache.org> on 2017/08/11 01:10:00 UTC
[jira] [Created] (KAFKA-5724) AbstractPartitionAssignor does not
take into consideration that partition number may start from non-zero
Allen Wang created KAFKA-5724:
---------------------------------
Summary: AbstractPartitionAssignor does not take into consideration that partition number may start from non-zero
Key: KAFKA-5724
URL: https://issues.apache.org/jira/browse/KAFKA-5724
Project: Kafka
Issue Type: Bug
Components: clients, consumer
Affects Versions: 0.11.0.0
Reporter: Allen Wang
In AbstractPartitionAssignor.assign(Cluster metadata, Map<String, Subscription> subscriptions), it invokes assign(partitionsPerTopic, subscriptions). It assumes that partition number starts from 0, and it constructs TopicPartition in the range of [0, partitionsPerTopic).
This assumption is not correct. The correct way to handle it is to follow the same approach in producer's DefaultPartitioner, where it uses [0, numberOfPartition) as an index to the actual partition.
There are use cases where partition number may not start from zero. It can happen if users use advanced tooling to manually craft the partition number when creating topics.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)