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 4E3FB2004A0 for ; Wed, 16 Aug 2017 23:45:13 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4C8FF168A1A; Wed, 16 Aug 2017 21:45: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 92DA7168A14 for ; Wed, 16 Aug 2017 23:45:12 +0200 (CEST) Received: (qmail 70840 invoked by uid 500); 16 Aug 2017 21:45:10 -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 70829 invoked by uid 99); 16 Aug 2017 21:45:10 -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; Wed, 16 Aug 2017 21:45:10 +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 B8584C37E2 for ; Wed, 16 Aug 2017 21:45:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id PxbpT0Q6L4sC for ; Wed, 16 Aug 2017 21:45:09 +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 603325FDFA for ; Wed, 16 Aug 2017 21:45:03 +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 5C842E0DFE for ; Wed, 16 Aug 2017 21:45:02 +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 F07C325386 for ; Wed, 16 Aug 2017 21:45:00 +0000 (UTC) Date: Wed, 16 Aug 2017 21:45:00 +0000 (UTC) From: "Ewen Cheslack-Postava (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (KAFKA-5567) With transformations that mutate the topic-partition committing offsets should to refer to the original topic-partition MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 16 Aug 2017 21:45:13 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5567. ------------------------------------------ Resolution: Fixed > With transformations that mutate the topic-partition committing offsets should to refer to the original topic-partition > ----------------------------------------------------------------------------------------------------------------------- > > Key: KAFKA-5567 > URL: https://issues.apache.org/jira/browse/KAFKA-5567 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect > Affects Versions: 0.10.2.0, 0.10.2.1, 0.11.0.0 > Reporter: Konstantine Karantasis > Assignee: Konstantine Karantasis > Priority: Blocker > Fix For: 0.11.0.1, 1.0.0 > > > When a chain of transformations (SMTs) that mutate a record's topic-partition is applied, then Connect is unable to map the transformed record to its original topic-partition. This affects committing offsets. > Currently, in order to reproduce the issue one could use the {{TimestampRouter}} transformation with a sink connector such as the {{FileStreamSinkConnector}}. > In this ticket we'll address the issue for connectors that don't manage/commit their offsets themselves. For the connectors that do such management, broader API changes are required to supply the connectors with the necessary information that will allow them to map a transformed record to the original. -- This message was sent by Atlassian JIRA (v6.4.14#64029)