From jira-return-9294-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Wed Jan 31 03:04:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id B695118061A for ; Wed, 31 Jan 2018 03:04:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A67C6160C55; Wed, 31 Jan 2018 02:04:05 +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 04A57160C53 for ; Wed, 31 Jan 2018 03:04:04 +0100 (CET) Received: (qmail 48364 invoked by uid 500); 31 Jan 2018 02:04:04 -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 48342 invoked by uid 99); 31 Jan 2018 02:04:04 -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, 31 Jan 2018 02:04:04 +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 90EC2D6270 for ; Wed, 31 Jan 2018 02:04:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id rom4S8Aq0ihh for ; Wed, 31 Jan 2018 02:04: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 2953D60ED6 for ; Wed, 31 Jan 2018 02:04: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 67710E018B for ; Wed, 31 Jan 2018 02:04: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 23D13240F6 for ; Wed, 31 Jan 2018 02:04:00 +0000 (UTC) Date: Wed, 31 Jan 2018 02:04:00 +0000 (UTC) From: "Matthias J. Sax (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KAFKA-6454) Allow timestamp manipulation in Processor API 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-6454?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6454: ----------------------------------- Description:=20 Atm, Kafka Streams only has a defined "contract" about timestamp propagatio= n at the Processor API level: all processor within a sub-topology, see the = timestamp from the input topic record and this timestamp will be used for a= ll result record when writing them to an topic, too. For the DSL and also for custom operator, it would be desirable to allow ti= mestamp manipulation for at Processor level for individual records that are= forwarded. KIP-251:=C2=A0https://cwiki.apache.org/confluence/display/KAFKA/KIP-251%3A+= Allow+timestamp+manipulation+in+Processor+API was: Atm, Kafka Streams only has a defined "contract" about timestamp propagatio= n at the Processor API level: all processor within a sub-topology, see the = timestamp from the input topic record and this timestamp will be used for a= ll result record when writing them to an topic, too. For the DSL and also for custom operator, it would be desirable to allow ti= mestamp manipulation for at Processor level for individual records that are= forwarded. > Allow timestamp manipulation in Processor API > --------------------------------------------- > > Key: KAFKA-6454 > URL: https://issues.apache.org/jira/browse/KAFKA-6454 > Project: Kafka > Issue Type: Improvement > Components: streams > Affects Versions: 1.0.0 > Reporter: Matthias J. Sax > Assignee: Matthias J. Sax > Priority: Major > Labels: kip > Fix For: 1.2.0 > > > Atm, Kafka Streams only has a defined "contract" about timestamp propagat= ion at the Processor API level: all processor within a sub-topology, see th= e timestamp from the input topic record and this timestamp will be used for= all result record when writing them to an topic, too. > For the DSL and also for custom operator, it would be desirable to allow = timestamp manipulation for at Processor level for individual records that a= re forwarded. > KIP-251:=C2=A0https://cwiki.apache.org/confluence/display/KAFKA/KIP-251%3= A+Allow+timestamp+manipulation+in+Processor+API -- This message was sent by Atlassian JIRA (v7.6.3#76005)