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

Posted to issues@flink.apache.org by "Ran Tao (Jira)" <ji...@apache.org> on 2023/03/03 17:45:00 UTC

[jira] [Created] (FLINK-31319) Inconsistent condition judgement about kafka partitionDiscoveryIntervalMs cause potential bug

Ran Tao created FLINK-31319:
-------------------------------

             Summary: 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
         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 enum:

!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. Finally cause
!image-2023-03-04-01-41-55-664.png|width=522,height=610!

bounded source can not signalNoMoreSplits.

Anyway，Both ends of the if condition should be mutually exclusive. WDYT?



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