From jira-return-11481-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Tue Apr 3 23:02:03 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 7310B18064D for ; Tue, 3 Apr 2018 23:02:03 +0200 (CEST) Received: (qmail 6456 invoked by uid 500); 3 Apr 2018 21:02:02 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 6445 invoked by uid 99); 3 Apr 2018 21:02:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2018 21:02:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 0DC66C0047 for ; Tue, 3 Apr 2018 21:02:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 38NA3K2VPJ51 for ; Tue, 3 Apr 2018 21:02:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0A8FF5F1B4 for ; Tue, 3 Apr 2018 21:02:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 81E99E0185 for ; Tue, 3 Apr 2018 21:02:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4A14925615 for ; Tue, 3 Apr 2018 21:02:00 +0000 (UTC) Date: Tue, 3 Apr 2018 21:02:00 +0000 (UTC) From: "Bill Bejeck (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (KAFKA-6729) KTable should use user source topics if possible and not create changelog topic MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)