Reputation: 122
Current Configuration
Problem
Question
Upvotes: 0
Views: 616
Reputation: 122
this issue is fixed in https://issues.apache.org/jira/browse/FLINK-28975. Using KafkaSource with WatermarkWithIdlness has an issue with marking the source as idle status.
Upvotes: 2
Reputation: 43454
The answers to your two questions are "No" and "No".
The new KafkaSource
does have different watermarking behavior compared to the legacy FlinkKafkaConsumer
in at least one case: when there are empty partitions. The old source detects empty partitions on startup and automatically marks them as idle, while the new source only detects idle partitions when it is used with the withIdleness
option.
If you have any empty partitions, this would explain why the join isn't producing any results.
Upvotes: 2