Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 52FAB200D2F for ; Wed, 18 Oct 2017 00:40:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 518C21609EC; Tue, 17 Oct 2017 22:40:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 97CCB1609EB for ; Wed, 18 Oct 2017 00:40:09 +0200 (CEST) Received: (qmail 80766 invoked by uid 500); 17 Oct 2017 22:40:08 -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 80755 invoked by uid 99); 17 Oct 2017 22:40:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Oct 2017 22:40:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 8E952180719 for ; Tue, 17 Oct 2017 22:40:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Oks8V0qcgi5G for ; Tue, 17 Oct 2017 22:40:06 +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 660305FBE9 for ; Tue, 17 Oct 2017 22:40:06 +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 56FFEE0E4A for ; Tue, 17 Oct 2017 22:40:05 +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 E030F243A1 for ; Tue, 17 Oct 2017 22:40:02 +0000 (UTC) Date: Tue, 17 Oct 2017 22:40:02 +0000 (UTC) From: "Andy Chambers (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-5836) Kafka Streams - API for specifying internal stream name on join MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 17 Oct 2017 22:40:10 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5836?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1620= 8523#comment-16208523 ]=20 Andy Chambers commented on KAFKA-5836: -------------------------------------- Agree that bumping the application id would resolve the issue by creating c= ompletely new internal topics. But v2 isn't really "changing" the input top= ics. It is reading two new topics (c and d) and processing those independen= tly of the original a and b. The required processing on a and b remains the= same and the state that has been built up remains valid and might take qui= te a while to build from scratch if you're using kafka as an event log. > Kafka Streams - API for specifying internal stream name on join > --------------------------------------------------------------- > > Key: KAFKA-5836 > URL: https://issues.apache.org/jira/browse/KAFKA-5836 > Project: Kafka > Issue Type: New Feature > Components: streams > Affects Versions: 0.11.0.0 > Reporter: Lovro Pand=C5=BEi=C4=87 > Labels: api, needs-kip > > Automatic topic name can be problematic in case of streams operation chan= ge/migration. > I'd like to be able to specify name of an internal topic so I can avoid c= reation of new stream and data "loss" when changing the Stream building. -- This message was sent by Atlassian JIRA (v6.4.14#64029)