[
https://issues.apache.org/jira/browse/BEAM-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821882#comment-16821882
]
Maximilian Michels commented on BEAM-7105:
------------------------------------------
Thanks for reporting. This looks like a duplicate of BEAM-3863. I've discussed
the problem and will be fixing it in the next days.
> AfterProcessingTime trigger not reliable; only fires on double numbers' event
> -----------------------------------------------------------------------------
>
> Key: BEAM-7105
> URL: https://issues.apache.org/jira/browse/BEAM-7105
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Affects Versions: 2.6.0
> Reporter: Jin Shen
> Priority: Major
>
> we use following statement in sql to configure the window trigger:
> sometimes it doesn't fire but the data is recorded in the window. and event
> come afterwards, the trigger fires with all the data together.
> I uploaded a video of screenshot on google drive. It will show the behavior
> of this.
> [https://drive.google.com/file/d/1wOo2s4ifAdwdAglbzOb0jEYZszsQPFjx/view?usp=sharing]
>
> {code:java}
> org.apache.beam.sdk.transforms.windowing.Window.configure()
>
> .triggering(org.apache.beam.sdk.transforms.windowing.AfterWatermark.pastEndOfWindow()
>
> .withEarlyFirings(org.apache.beam.sdk.transforms.windowing.AfterProcessingTime.pastFirstElementInPane().plusDelayOf(org.joda.time.Duration.millis(0)))
>
> .withLateFirings(org.apache.beam.sdk.transforms.windowing.AfterProcessingTime.pastFirstElementInPane().plusDelayOf(org.joda.time.Duration.millis(20000))))
> .withAllowedLateness(org.joda.time.Duration.millis(3600000),
> org.apache.beam.sdk.transforms.windowing.Window.ClosingBehavior.valueOf("FIRE_IF_NON_EMPTY"))
>
> .withOnTimeBehavior(org.apache.beam.sdk.transforms.windowing.Window.OnTimeBehavior.valueOf("FIRE_IF_NON_EMPTY")).accumulatingFiredPanes()
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
