kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Bejeck (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (KAFKA-6729) KTable should use user source topics if possible and not create changelog topic
Date Tue, 03 Apr 2018 21:02:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-6729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bill Bejeck reassigned KAFKA-6729:
----------------------------------

    Assignee: Bill Bejeck

> 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
>            Assignee: Bill Bejeck
>            Priority: Critical
>             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)

Mime
View raw message