Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Today Streams make all state stores to be backed by a changelog topic by default unless users overrides it by disableLogging when creating the state store / materializing the KTable. However there are a few cases where a separate changelog topic would not be required as we can re-use an existing topic for that. This ticket summarize a specific issue that can be optimized:
Consider the case when a KTable is materialized and then sent directly into a sink topic with the same key, e.g.
table1 = stream.groupBy(...).aggregate("state1").to("topic2");
Then we do not need to create a state1-changelog but can just use topic2 as its changelog.
Attachments
Issue Links
- relates to
-
KAFKA-6761 Reduce Kafka Streams Footprint
- Resolved
- links to