beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Feldhaus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow
Date Sat, 18 Mar 2017 13:17:42 GMT

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

Tobias Feldhaus commented on BEAM-1718:
---------------------------------------

When batch-processing, shifting back in time is normal and crucial for me (especially when
windowing elements to get them into the right partition in BigQuery). When this method gets
deprecated, how should such cases be handled in the future then?

> 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