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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 16:33:14 UTC

[GitHub] [beam] kennknowles opened a new issue, #18190: Timestamp precision and byte representation should be consistent across SDKs

kennknowles opened a new issue, #18190:
URL: https://github.com/apache/beam/issues/18190

   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.
   
   Imported from Jira [BEAM-1524](https://issues.apache.org/jira/browse/BEAM-1524). Original Jira may contain additional context.
   Reported by: vikasrk.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org