[
https://issues.apache.org/jira/browse/BEAM-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132463#comment-17132463
]
Beam JIRA Bot commented on BEAM-1524:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Vikas Kedigehalli
> Priority: P2
> Labels: stale-assigned
>
> 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)
