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 9EB2D200C22 for ; Tue, 21 Feb 2017 23:40:48 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9D663160B74; Tue, 21 Feb 2017 22:40:48 +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 E8D5C160B4F for ; Tue, 21 Feb 2017 23:40:47 +0100 (CET) Received: (qmail 65647 invoked by uid 500); 21 Feb 2017 22:40:47 -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 65638 invoked by uid 99); 21 Feb 2017 22:40:47 -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; Tue, 21 Feb 2017 22:40:47 +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 C5F20C67D5 for ; Tue, 21 Feb 2017 22:40:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.999 X-Spam-Level: X-Spam-Status: No, score=0.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.001] 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 wNhw-UxAC0BL for ; Tue, 21 Feb 2017 22:40:46 +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 A06865F640 for ; Tue, 21 Feb 2017 22:40:45 +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 BAD93E0A0D for ; Tue, 21 Feb 2017 22:40:44 +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 274FB24129 for ; Tue, 21 Feb 2017 22:40:44 +0000 (UTC) Date: Tue, 21 Feb 2017 22:40:44 +0000 (UTC) From: "Vikas Kedigehalli (JIRA)" To: commits@beam.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (BEAM-1524) Timestamp precision should be consistent across SDKs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 21 Feb 2017 22:40:48 -0000 Vikas Kedigehalli created BEAM-1524: --------------------------------------- Summary: Timestamp precision should be consistent across SDKs Key: BEAM-1524 URL: https://issues.apache.org/jira/browse/BEAM-1524 Project: Beam Issue Type: Improvement Components: runner-core, sdk-java-core, sdk-py Reporter: Vikas Kedigehalli Assignee: Kenneth Knowles Runners cannot have a timestamp precision that is lesser than what a SDK uses. Also with Fn API a runner should be able to support multiple SDKs that maybe written in different languages. It is important that we standardize the precision of timestamp to ensure that runners are compatible across all the SDKs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)