[
https://issues.apache.org/jira/browse/FLINK-33224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774672#comment-17774672
]
Kanthi Vaidya edited comment on FLINK-33224 at 10/12/23 7:49 PM:
-----------------------------------------------------------------
[~martijnvisser] I am talking about Apache Flink 1.14.6. Is this not supported
anymore? What is the smallest version of flink that you support?
https://flink.apache.org/2022/09/28/apache-flink-1.14.6-release-announcement/
was (Author: JIRAUSER302517):
[~martijnvisser] I am talking about Apache Flink 1.14.6. Is this not supported
anymore? What is the smallest version of flink that you support?
> Flink Batch Job does not complete when using Kafka topics with empty
> partitions
> --------------------------------------------------------------------------------
>
> Key: FLINK-33224
> URL: https://issues.apache.org/jira/browse/FLINK-33224
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.14.6
> Reporter: Kanthi Vaidya
> Priority: Major
>
> Kafka Source Connector no longer throws an exception when running a flink job
> in batch mode when using Kafka topics with empty partitions. However, flink
> does not emit the final watermark of Long.MAX_VALUE even if all the messages
> have been read. Note that we are using bounded sources, since that is a
> requirement for batch mode. It appears that the Kafka consumer continues to
> run even though the source is bounded.
> Same is the case with an empty topic. We do have optional sources, where data
> need not be present all the time. However if we mark the source as bounded,
> the Kafka connector should recognize empty partitions and mark it as
> completed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
