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 7133F200C6F for ; Tue, 9 May 2017 08:42:13 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6FC85160BB6; Tue, 9 May 2017 06:42:13 +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 B604F160BB3 for ; Tue, 9 May 2017 08:42:12 +0200 (CEST) Received: (qmail 11028 invoked by uid 500); 9 May 2017 06:42:06 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 11017 invoked by uid 99); 9 May 2017 06:42:06 -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; Tue, 09 May 2017 06:42:06 +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 64A441AF961 for ; Tue, 9 May 2017 06:42:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[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 (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id fQiNJa0zsgmG for ; Tue, 9 May 2017 06:42:05 +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 86CE85FBBB for ; Tue, 9 May 2017 06:42:05 +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 EB7C9E0BE1 for ; Tue, 9 May 2017 06:42:04 +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 A041A21DF4 for ; Tue, 9 May 2017 06:42:04 +0000 (UTC) Date: Tue, 9 May 2017 06:42:04 +0000 (UTC) From: "Jason Gustafson (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-5202) Handle topic deletion for ongoing transactions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 09 May 2017 06:42:13 -0000 Jason Gustafson created KAFKA-5202: -------------------------------------- Summary: Handle topic deletion for ongoing transactions Key: KAFKA-5202 URL: https://issues.apache.org/jira/browse/KAFKA-5202 Project: Kafka Issue Type: Sub-task Reporter: Jason Gustafson If a topic is deleted, we should remove its partitions from ongoing transactions. If the topic has already begun rolling forward, we have to let it continue for the rest of the included partitions, but we have the option of failing a transaction which is yet to be committed or aborted. -- This message was sent by Atlassian JIRA (v6.3.15#6346)