Hi,
I agree with some of Jan's points here. Interactive queries are a nice to have,
but not worth sacrificing clean interfaces over.
It's not the main use case of Kafka Streams and implementing it via a
getQueryHandle on KTables means the related logic doesn't spread everywhere but
instead trul
Hi,
I suggest that Merger should extend Aggregator.
reason:
Both classes usually do very similar things. A merger takes two sessions and
combines them, an aggregator takes an existing session and aggregates new
values into it.
in some use cases it is actually the same thing, e.g.:
-> .map() to
