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
>From the source code in KGroupedTableImpl, the subtractor is always called
before the adder. By not guaranteeing the order, I think the devs meant
that it might change on future versions of Kafka Streams (although I'd
think it's unlikely to).
I have use cases similars with your example, and that