[
https://issues.apache.org/jira/browse/FLINK-31319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696308#comment-17696308
]
Ran Tao commented on FLINK-31319:
---------------------------------
Reproduce: Using bounded kafka, set partitionDiscoveryIntervalMs=0, then job
never quit. [~martijnvisser] [~renqs] WDYT? it's maybe a big bug.
> Inconsistent condition judgement about kafka partitionDiscoveryIntervalMs
> cause potential bug
> ---------------------------------------------------------------------------------------------
>
> Key: FLINK-31319
> URL: https://issues.apache.org/jira/browse/FLINK-31319
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.16.1
> Reporter: Ran Tao
> Priority: Critical
> Labels: pull-request-available
> Attachments: image-2023-03-04-01-37-29-360.png,
> image-2023-03-04-01-39-20-352.png, image-2023-03-04-01-40-44-124.png,
> image-2023-03-04-01-41-55-664.png
>
>
> As kafka option description, partitionDiscoveryIntervalMs <=0 means disabled.
> !image-2023-03-04-01-37-29-360.png|width=781,height=147!
> just like start kafka enumerator:
> !image-2023-03-04-01-39-20-352.png|width=465,height=311!
> but inner
> handlePartitionSplitChanges use error if condition( < 0):
> !image-2023-03-04-01-40-44-124.png|width=576,height=237!
>
> it will cause noMoreNewPartitionSplits can not be set to true.
> !image-2023-03-04-01-41-55-664.png|width=522,height=610!
> Finally cause bounded source can not signalNoMoreSplits and quit.
> Besides，Both ends of the if condition should be mutually exclusive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
