[jira] [Created] (KAFKA-6035) Avoid creating changelog topics for state stores that are directly piped to a sink topic

["Guozhang Wang (JIRA)" <ji...@apache.org>]

Guozhang Wang created KAFKA-6035:
------------------------------------

             Summary: Avoid creating changelog topics for state stores that are directly piped to a sink topic
                 Key: KAFKA-6035
                 URL: https://issues.apache.org/jira/browse/KAFKA-6035
             Project: Kafka
          Issue Type: Sub-task
            Reporter: Guozhang Wang


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.

{code}
table1 = stream.groupBy(...).aggregate("state1").to("topic2");
{code}

Then we do not need to create a {{state1-changelog}} but can just use {{topic2}} as its changelog.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)