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 2020/04/05 18:55:05 UTC

[GitHub] [beam] reuvenlax commented on issue #6315: [BEAM-5250] Fix GlobalWindow's max timestamp in Python SDK

reuvenlax commented on issue #6315: [BEAM-5250] Fix GlobalWindow's max timestamp in Python SDK
URL: https://github.com/apache/beam/pull/6315#issuecomment-609464542
 
 
   IIRC there were multiple bugs caused by converting max timestamp from int64 -> double and then back to int64, as high int64 values cannot be precisely represented as an IEEE double (so max int64 comes back as a negative number if you round trip it through a double). I believe the current Java max timestamp was chosen because it's a value that can be represented precisely in both an int64 and a double.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services