From issues-return-75871-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Mon Sep 24 20:22: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 1BB1C180649 for ; Mon, 24 Sep 2018 20:22:02 +0200 (CEST) Received: (qmail 74616 invoked by uid 500); 24 Sep 2018 18:22:02 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 74606 invoked by uid 99); 24 Sep 2018 18:22:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2018 18:22:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CDD16C6CF7 for ; Mon, 24 Sep 2018 18:22:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 0ZGHjFoOSFLq for ; Mon, 24 Sep 2018 18:22: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 186035F3CE for ; Mon, 24 Sep 2018 18:22: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 AE880E0D9F for ; Mon, 24 Sep 2018 18:22: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 72C8323FA1 for ; Mon, 24 Sep 2018 18:22:00 +0000 (UTC) Date: Mon, 24 Sep 2018 18:22:00 +0000 (UTC) From: "Nikolay Izhikov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-7065) Cannot use multiple Ignite Kafka Sink Connectors 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/IGNITE-7065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7065: ------------------------------------ Fix Version/s: (was: 2.7) 2.8 > Cannot use multiple Ignite Kafka Sink Connectors > ------------------------------------------------- > > Key: IGNITE-7065 > URL: https://issues.apache.org/jira/browse/IGNITE-7065 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.3 > Reporter: Alexey Kukushkin > Priority: Major > Fix For: 2.8 > > > Stopping an Ignite Kafka sink connector makes other connectors deployed in the same worker unusable. As a result we cannot stream different topics in different caches since connector support streaming to single cache only. > See http://apache-ignite-users.70518.x6.nabble.com/Issues-with-multiple-kafka-connectors-questions-regarding-ignite-caches-tc18297.html for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)