When performing aggregations that require repartitioning and the repartition topic name is specified, and using the resulting KGroupedStream for multiple operations i.e.
If optimizations aren't enabled, Streams will attempt to build two repartition topics of the same name resulting in a failure creating the topology.
However, we have enough information to re-use the existing repartition node via graph nodes used for building the intermediate representation of the topology. This ticket will make the
behavior of reusing a KGroupedStream consistent regardless if optimizations are turned on or not.