[
https://issues.apache.org/jira/browse/FLINK-29128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597313#comment-17597313
]
Mason Chen commented on FLINK-29128:
------------------------------------
I wonder if we did not solve "empty partitions" correctly.
In the bounded case, yes, we don't care about these empty splits. But for the
unbounded case, the empty splits may eventually contain data, so we should
assign them.
> Uncatch IllegalStateException found when log split changes handling result in
> KafkaPartitionSplitReader
> -------------------------------------------------------------------------------------------------------
>
> Key: FLINK-29128
> URL: https://issues.apache.org/jira/browse/FLINK-29128
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.14.5, 1.15.2
> Reporter: Leo zhang
> Assignee: Leo zhang
> Priority: Minor
> Labels: pull-request-available
>
> When logger is set to debug mode,
> KafkaPartitionSplitReader#maybeLogSplitChangesHandingResult log the handing
> result of all SplitsChange<KafkaPartitionSplit>, and the handling result
> include the kafka partition's starting offset, which is get from kafka
> api(consumer.position).
> When a SplitsChange<KafkaPartitionSplit> is a empty split,it will be
> removed(unassign partition), IllegalStateException will be thrown by
> consumer.position, since we can only check the position for partitions
> assigned to the consumer.And this exception has not been catch, and is
> rethrown as RuntimeExption, which lead to a failure of the application's
> execution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
