Description
With KIP-182 we reworked Streams API largely and introduced a regression into 1.0 code base. If a KTable is populated from a source topic, ie, StreamsBuilder.table() – the KTable does create its own changelog topic. However, in older releases (0.11 or older), we don't create a changelog topic but use the user specified source topic instead.
We want to reintroduce this optimization to reduce the load (storage and write) on the broker side for this case.
Attachments
Issue Links
- contains
-
KAFKA-7424 State stores restoring from changelog topic not the source topic
- Resolved
- links to