[
https://issues.apache.org/jira/browse/BEAM-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17179921#comment-17179921
]
Beam JIRA Bot commented on BEAM-1524:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> 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)
