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

Posted to issues@beam.apache.org by "Danny McCormick (Jira)" <ji...@apache.org> on 2022/06/03 15:08:00 UTC

[jira] [Commented] (BEAM-29) Bound Instant values used as timestamps at TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE

    [ https://issues.apache.org/jira/browse/BEAM-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545938#comment-17545938 ] 

Danny McCormick commented on BEAM-29:
-------------------------------------

This isn't actually real, but this issue has been migrated to https://github.com/apache/beam/issues/17849

> Bound Instant values used as timestamps at TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE
> --------------------------------------------------------------------------------------
>
>                 Key: BEAM-29
>                 URL: https://issues.apache.org/jira/browse/BEAM-29
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: P3
>              Labels: Clarified
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)