opened
danishgarg
username_0
However, when using kafka streams binder, the binder automatically creates a -repartition topic because the serialization/deserialization code uses the **map** function on the stream. This marks the stream for re-partitioning and any subsequent group by operation done by client code results in creation of a repartition topic.
The use of Spring cloud stream should ideally be transparent and side effect free. Since there is no serialization/deserialization done by the framework when it comes to keys, there is a case to use **mapValues** instead of **map** when doing message value serialization/deserialization. This will prevent creation of any extra topics.
Kafka streams binder creates a -repartition topic even though no key modifying operations are done by client code
issue
created
sobychacko
username_1
@username_0 Thank you for reporting the issue. We will look into it soon. In the meantime, contributions are welcomed!
comment
created
sabbyanandan
username_2
Hi, @username_0. Good write-up! Thanks for bringing it to our attention. Let us know if you have any other suggestions for improvements.
comment
closed
sobychacko
username_1
issue