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 11FF5200D16 for ; Tue, 26 Sep 2017 00:36:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 109631609ED; Mon, 25 Sep 2017 22:36:06 +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 5D2481609BB for ; Tue, 26 Sep 2017 00:36:05 +0200 (CEST) Received: (qmail 71270 invoked by uid 500); 25 Sep 2017 22:36:04 -0000 Mailing-List: contact commits-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list commits@beam.apache.org Received: (qmail 71261 invoked by uid 99); 25 Sep 2017 22:36:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Sep 2017 22:36:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E3570182BE5 for ; Mon, 25 Sep 2017 22:36:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id CAen4AKySo-E for ; Mon, 25 Sep 2017 22:36:03 +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 A1E8860D9C for ; Mon, 25 Sep 2017 22:36:02 +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 C6C59E0F6F for ; Mon, 25 Sep 2017 22:36:01 +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 BBE322429F for ; Mon, 25 Sep 2017 22:36:00 +0000 (UTC) Date: Mon, 25 Sep 2017 22:36:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: commits@beam.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (BEAM-2467) KinesisIO watermark based on approximateArrivalTimestamp MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Sep 2017 22:36:06 -0000 [ https://issues.apache.org/jira/browse/BEAM-2467?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16179= 888#comment-16179888 ]=20 ASF GitHub Bot commented on BEAM-2467: -------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/beam/pull/3851 > KinesisIO watermark based on approximateArrivalTimestamp > -------------------------------------------------------- > > Key: BEAM-2467 > URL: https://issues.apache.org/jira/browse/BEAM-2467 > Project: Beam > Issue Type: Improvement > Components: sdk-java-extensions > Reporter: Pawe=C5=82 Kaczmarczyk > Assignee: Pawe=C5=82 Kaczmarczyk > > In Kinesis we can start reading the stream at some point in the past duri= ng the retention period (up to 7 days). With current approach for setting r= ecord's timestamp and watermark (both are always set to current time, i.e. = Instant.now()), we can't observe the actual position in the stream. > So the idea is to change this behaviour and set the record timestamp base= d on the [ApproximateArrivalTimestamp|http://docs.aws.amazon.com/kinesis/la= test/APIReference/API_Record.html#Streams-Type-Record-ApproximateArrivalTim= estamp]. Watermark will be set accordingly to the last read record's timest= amp.=20 > ApproximateArrivalTimestamp is still some approximation and may result in= having records with out-of-order timestamp's which in turn may result in s= ome events marked as late. This however should not be a frequent issue and = even if it happens it should be a matter of milliseconds or seconds so can = be handled even with a tiny allowedLateness setting -- This message was sent by Atlassian JIRA (v6.4.14#64029)