You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2017/08/24 21:06:00 UTC
[jira] [Assigned] (BEAM-1408) outputWithTimestamp() accepts
timestamps that will fail preconditions
[ https://issues.apache.org/jira/browse/BEAM-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davor Bonaci reassigned BEAM-1408:
----------------------------------
Assignee: (was: Davor Bonaci)
> 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: Minor
>
> 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
(v6.4.14#64029)