You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/02 17:08:39 UTC

[jira] [Updated] (BEAM-1524) Timestamp precision and byte representation should be consistent across SDKs

     [ https://issues.apache.org/jira/browse/BEAM-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Beam JIRA Bot updated BEAM-1524:
--------------------------------
    Priority: P3  (was: P2)

> Timestamp precision and byte representation 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-core
>            Reporter: Vikas Kedigehalli
>            Priority: P3
>              Labels: stale-P2
>
> 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.
> NOTE: Timestamps are shifted such that lexicographic ordering of the bytes corresponds to chronological order. This also needs to be consistent across SDKs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)