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 9856D200D06 for ; Mon, 25 Sep 2017 20:33:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 96F201609E9; Mon, 25 Sep 2017 18:33:07 +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 E48321609B5 for ; Mon, 25 Sep 2017 20:33:06 +0200 (CEST) Received: (qmail 39851 invoked by uid 500); 25 Sep 2017 18:33:06 -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 39830 invoked by uid 99); 25 Sep 2017 18:33: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; Mon, 25 Sep 2017 18:33: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 B17141A3AF0 for ; Mon, 25 Sep 2017 18:33:05 +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 PLHsw6S7VYRt for ; Mon, 25 Sep 2017 18:33: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 D42A25F4A9 for ; Mon, 25 Sep 2017 18:33:04 +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 09163E0B20 for ; Mon, 25 Sep 2017 18:33: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 4D4E224256 for ; Mon, 25 Sep 2017 18:33:02 +0000 (UTC) Date: Mon, 25 Sep 2017 18:33:02 +0000 (UTC) From: "Apurva Mehta (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KAFKA-5888) Transactions system test should check for message order MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Sep 2017 18:33:07 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5888: -------------------------------- Fix Version/s: (was: 1.1.0) 1.0.0 > Transactions system test should check for message order > ------------------------------------------------------- > > Key: KAFKA-5888 > URL: https://issues.apache.org/jira/browse/KAFKA-5888 > Project: Kafka > Issue Type: Sub-task > Reporter: Apurva Mehta > Assignee: Apurva Mehta > Labels: exactly-once > Fix For: 1.0.0 > > > Currently, the transactions system test doesn't check for correct ordering of the messages in a transaction. With KAFKA-5494, we can have multiple inflight requests for a single transaction, which could yield to out of order messages in the log if there are bugs. So we should assert that order is maintained in our system tests. -- This message was sent by Atlassian JIRA (v6.4.14#64029)