Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-6034 Streams DSL to Processor Topology Translation Improvements
  3. KAFKA-6035

Avoid creating changelog topics for state stores that are directly piped to a sink topic

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: streams
    • Labels:
      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

            Activity

              People

              • Assignee:
                jeyhunkarimov Jeyhun Karimov
                Reporter:
                guozhang Guozhang Wang
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: