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 15:07:44 UTC

[GitHub] [beam] damccorm opened a new issue, #17849: Bound Instant values used as timestamps at TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE

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

   Today the Java SDK allows arbitrary Instant values. If large magnitude Instant values reach a runner with greater precision but the same modulus for its representation, overflow will occur.
   
   Imported from Jira [BEAM-29](https://issues.apache.org/jira/browse/BEAM-29). Original Jira may contain additional context.
   Reported by: kenn.


-- 
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

[GitHub] [beam] damccorm closed issue #17849: Bound Instant values used as timestamps at TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE

Posted by GitBox <gi...@apache.org>.

damccorm closed issue #17849: Bound Instant values used as timestamps at TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE
URL: https://github.com/apache/beam/issues/17849


-- 
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

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