From jira-return-10382-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Fri Mar 2 03:36:05 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 DEE1C18064D for ; Fri, 2 Mar 2018 03:36:04 +0100 (CET) Received: (qmail 93235 invoked by uid 500); 2 Mar 2018 02:36:03 -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 93220 invoked by uid 99); 2 Mar 2018 02:36:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2018 02:36:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id CED2C1A09CD for ; Fri, 2 Mar 2018 02:36:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id KbZNh-qAreCt for ; Fri, 2 Mar 2018 02:36:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 475E45F126 for ; Fri, 2 Mar 2018 02:36: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 7F910E022F for ; Fri, 2 Mar 2018 02:36: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 2FE8624762 for ; Fri, 2 Mar 2018 02:36:00 +0000 (UTC) Date: Fri, 2 Mar 2018 02:36:00 +0000 (UTC) From: "Matthias J. Sax (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-4936) Allow dynamic routing of output records MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-4936?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1638= 3038#comment-16383038 ]=20 Matthias J. Sax commented on KAFKA-4936: ---------------------------------------- If you provide an unknown topic name for an output topic, the topic with ei= ther be created if auto-topic create is enabled, or a runtime error occurs.= StreamsBuilder does not check the existence of topics. I tend to agree, that auto.topic create is a "tricky feature". The main que= stion is the following: if we argue, that auto topic creation should not be= used, this implies that all output topic must be know in advance because u= sers need to create them. And thus, users can also use the {{branch()}}=C2= =A0operator and don't need "auto routing" in the first place. Thus, it seem= s that people asking for this feature actually assume that auto-topic creat= e is enabled =E2=80=93 otherwise I cannot explain why one would need this f= eature? I am still not convinced about the overall story / need for this. We also w= ould need a KIP and a discussion on the mailing list. Thus, it might make m= ore sense to do this discussion first, before starting to write the code = =E2=80=93 we might decide that we don't want this for the mentioned reasons= .=C2=A0When we go the feature request, we just create the Jira to track it = =E2=80=93 but in retrospective, I am not sure about it anymore. > Allow dynamic routing of output records > --------------------------------------- > > Key: KAFKA-4936 > URL: https://issues.apache.org/jira/browse/KAFKA-4936 > Project: Kafka > Issue Type: Improvement > Components: streams > Reporter: Matthias J. Sax > Priority: Major > Labels: needs-kip > > Currently, all used output topics must be know beforehand, and thus, it's= not possible to send output records to topic in a dynamic fashion. > There have been couple of request for this feature and we should consider= adding it. There are many open questions however, with regard to topic cre= ation and configuration (replication factor, number of partitions) etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)