You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Nitay Kufert (Jira)" <ji...@apache.org> on 2020/01/02 09:14:00 UTC

[jira] [Comment Edited] (KAFKA-9335) java.lang.IllegalArgumentException: Number of partitions must be at least 1.

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

Nitay Kufert edited comment on KAFKA-9335 at 1/2/20 9:13 AM:
-------------------------------------------------------------

In the example I provided, the exception is thrown over the following key: 
 missing-partitions-example-odd_store_2-repartition

And regarding the number of partitions - the topic can't be found so I guess that why it has 0 partitions.

 


was (Author: nitay.k):
In the example I provided, the exception is thrown over the following key: 
missing-partitions-example-odd_store_2-repartition

And regarding the number of partitions - the topic can't be found so I guess that why it has 0 partitions

> java.lang.IllegalArgumentException: Number of partitions must be at least 1.
> ----------------------------------------------------------------------------
>
>                 Key: KAFKA-9335
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9335
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.4.0
>            Reporter: Nitay Kufert
>            Priority: Major
>              Labels: bug
>
> Hey,
> When trying to upgrade our Kafka streams client to 2.4.0 (from 2.3.1) we encountered the following exception: 
> {code:java}
> java.lang.IllegalArgumentException: Number of partitions must be at least 1.
> {code}
> It's important to notice that the exact same code works just fine at 2.3.1.
>  
> I have created a "toy" example which reproduces this exception:
> [https://gist.github.com/nitayk/50da33b7bcce19ad0a7f8244d309cb8f]
> and I would love to get some insight regarding why its happening / ways to get around it
>  
> Thanks



--
This message was sent by Atlassian Jira
(v8.3.4#803005)