You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2018/03/30 22:59:00 UTC
[jira] [Created] (KAFKA-6729) KTable should use user source topics
if possible and not create changelog topic
Matthias J. Sax created KAFKA-6729:
--------------------------------------
Summary: KTable should use user source topics if possible and not create changelog topic
Key: KAFKA-6729
URL: https://issues.apache.org/jira/browse/KAFKA-6729
Project: Kafka
Issue Type: Bug
Components: streams
Affects Versions: 1.0.0
Reporter: Matthias J. Sax
Fix For: 1.2.0
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)