Yes, but that information would have to "bubble" up from the downstream
operator to the source, which is not possible right now.
On Sun, 12 Feb 2017 at 17:15 Jonas wrote:
> For 2: You can also NOT read the Source (i.e. Kafka) while doing that. This
> way you don't have to buffer.
>
>
>
> --
> Vi
For 2: You can also NOT read the Source (i.e. Kafka) while doing that. This
way you don't have to buffer.
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Start-streaming-tuples-depending-on-another-streams-rate-tp11542p11590.html
Sent from th
voked with the special event, you can toggle
> logic in flatMap2 to actually start doing stuff.
>
> This has the issue that while stream A is being processed, I lose tuples
> from stream B because it is not "stopped". I think my use case is currently
> not really doable in
Tzu-Li (Gordon) Tai wrote
> Stream A has a rate of 100k tuples/s. After processing the whole Kafka
> queue, the rate drops to 10 tuples/s.
Absolutely correct.
Tzu-Li (Gordon) Tai wrote
> So what you are looking for is that flatMap2 for stream B only doing work
> after the job reaches the latest re
Hi Jonas,
A few things to clarify first:
Stream A has a rate of 100k tuples/s. After processing the whole Kafka queue,
the rate drops to 10 tuples/s.
From this description it seems like the job is re-reading from the beginning
from the topic, and once you reach the latest record at the head of
