[
https://issues.apache.org/jira/browse/BEAM-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932906#comment-15932906
]
Thomas Groh commented on BEAM-1718:
-----------------------------------
Most of the time, elements from a {{BoundedSource}} will be emitted with a
timestamp equal to negative infinity, so you will be able to shift them
forwards in time to the appropriate point. Using the {{OutputTimeFn}} will
permit elements to not be shifted further forwards in time, but generally
timestamp assignment should be only-once (with aggregations emitting with a
timestamp appropriate for the aggregation, based on the {{OutputTimeFn}}).
For unbounded sources, we will need some way to shift elements backwards in
time, but that also requires holding the watermark so those elements don't
become late within the unified model. That requires more collaboration with a
Runner.
> 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)
