Something like this -- the idea would be to set a "flag" on the `KGroupedStream` (same for `KGroupedTable`?) after the first `count()/reduce()/aggregate()` is executed and to remember the created repartition topic. And for this case, consecutive `count()/reduce()/aggregate()` would skip creating a new changelog topic but reuse the already created one.
For backward compatibility, we would only do this if `Grouped.as` is specified. It might be a little bit hacky, but might be worth it... Thoughts? [ Full content available at: https://github.com/apache/kafka/pull/5709 ] This message was relayed via gitbox.apache.org for [email protected]
