Daniel,
maybe I did not extract your test logic correctly form you code. It's a
long piece... However, I do see two order-events:
>>> playOrderstream(clock, user, 2, "Japan");
>>> playOrderstream(clock, user, 6, "Peru");
Maybe your test logic is somehow not correct (just a wild guess).
Hi Matthias,
Thanks for your reply. I have a few questions on your comments:
1) I understand the records are updated as Ktables work as changelogs.
However there is a single record in my source stream which means that even
if the aggregate is updated 2+ times the output should still be the same.
Hi,
there are two things:
1) aggregation operator produce an output record each time the aggregate
is is updates. Thus, you would get 6 record in you example. At the same
time, we deduplicate consecutive outputs with an internal cache. And the
cache is flushed non-mechanistically (either partly f
