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

Posted to jira@kafka.apache.org by "huxihx (JIRA)" <ji...@apache.org> on 2017/09/11 07:46:01 UTC

[jira] [Commented] (KAFKA-5860) Prevent non-consecutive partition ids

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

huxihx commented on KAFKA-5860:
-------------------------------

Seems it's related to [KAFKA-5724|https://issues.apache.org/jira/browse/KAFKA-5724]. Can we confirm that Kafka does not allow non-consecutive or non zero-based partition ids?

> Prevent non-consecutive partition ids
> -------------------------------------
>
>                 Key: KAFKA-5860
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5860
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Tom Bentley
>            Priority: Minor
>
> It is possible to create non-consecutive partition ids via AdminClient.createTopics() and the kafka-topics.sh. It's not clear that this has any use cases, nor that it is well tested. 
> Since people generally assume partition ids will be consecutive it is likely to be a cause of bugs in both Kafka and user code.
> We should remove the ability to create topics with non-consecutive partition ids.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)