beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neelesh Srinivas Salian (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-29) Bound Instant values used as timestamps at TIMESTAMP_MIN_VALUE and TIMESTAMP_MAX_VALUE
Date Sun, 11 Dec 2016 00:28:58 GMT

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

Neelesh Srinivas Salian commented on BEAM-29:
---------------------------------------------

This looks like it has been solved in incubator-beam/sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/windowing/BoundedWindow.java
Need to close this [~kenn]

> 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
>            Assignee: Neelesh Srinivas Salian
>            Priority: Minor
>
> 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
(v6.3.4#6332)

Mime
View raw message