beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow
Date Wed, 15 Mar 2017 02:31:41 GMT

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

Kenneth Knowles commented on BEAM-1718:
---------------------------------------

Is this a basic overflow error where we should do the checking, or is it https://bugs.openjdk.java.net/browse/JDK-8074032?

> Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow
> -----------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-1718
>                 URL: https://issues.apache.org/jira/browse/BEAM-1718
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>    Affects Versions: 0.5.0
>            Reporter: Tobias Feldhaus
>            Assignee: Thomas Groh
>
> Overriding getAllowedTimestampSkew() in DoFn and returning Duration.millis(Long.MAX_VALUE)
(as suggested in the JavaDoc for allowing infinite skew) causes an Overflow/Underflow



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message