Hi Alexandre, thanks for your reply. I updated my example to produce a
message to the compacted topic ("table") at a lower timestamp, but I'm
still not getting the expected result unfortunately. The scenario is now:
1. Message published to A ("input") with timestamp t_0
2. Three seconds of wall cl
Hi Derek,
What max.task.idle.ms does is set a wait time for the stream application to
wait for new messages when one or more
input topics have no messages after a poll. In your case, the application
polls for the first time and finds a message on
topic A ("input") and no messages on topic B ("tabl
unsubscribe
On Mon, Aug 29, 2022 at 8:56 AM Derek Mok wrote:
> Hi, I'd like some help with understanding how exactly max.task.idle.ms
> works. I have a topology that consumes from an input topic A, and a join
> operator that enriches the topic A messages with a KTable from a compacted
> topic B.
Hi, I'd like some help with understanding how exactly max.task.idle.ms
works. I have a topology that consumes from an input topic A, and a join
operator that enriches the topic A messages with a KTable from a compacted
topic B. The enriched messages are output to topic C.
If I set max.task.idle.ms
