[
https://issues.apache.org/jira/browse/BEAM-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546306#comment-17546306
]
Kenneth Knowles commented on BEAM-1408:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18188
> outputWithTimestamp() accepts timestamps that will fail preconditions
> ---------------------------------------------------------------------
>
> Key: BEAM-1408
> URL: https://issues.apache.org/jira/browse/BEAM-1408
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Andy Xu
> Priority: P3
> Labels: Clarified
>
> We have accidentally created events with *wrong* timestamps in the future
> which are accepted by
> outputWithTimestamp(), but will fail at a later step:
> java.lang.IllegalStateException: Timer 472976-06-15T20:09:57.269Z is beyond
> end-of-time
> at Preconditions.checkState(Preconditions.java:199)
> at
> ReduceFnRunner.scheduleEndOfWindowOrGarbageCollectionTimer(ReduceFnRunner.java:1050)
> [...]
> Would it make sense to implement a check already at outputWithTimestamp()
> level to fail early?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
