[
https://issues.apache.org/jira/browse/BEAM-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505385#comment-16505385
]
Batkhuyag Batsaikhan commented on BEAM-4507:
--------------------------------------------
The solution around this problem was to add enough allowed lateness to the new
fixed windows, so that the windows don't expire when a late element arrived.
Closing this Jira now.
> Objects that have Fixed Window after a Global Window disappear in Directrunner
> ------------------------------------------------------------------------------
>
> Key: BEAM-4507
> URL: https://issues.apache.org/jira/browse/BEAM-4507
> Project: Beam
> Issue Type: Improvement
> Components: runner-direct
> Affects Versions: 2.4.0
> Reporter: Reza ardeshir rokni
> Assignee: Batkhuyag Batsaikhan
> Priority: Major
>
> 1- Create a elements that go into a combinar and then drops into a Keyed
> Global Window, on entry setup a timer.
> Have the OnTime function:
> 1- c.output the original element with a timestamp == to the original timestamp
> 2- Create a new timestamp with element in the next window....
> 2- LOG the output in a DoFn after the keyed state code, you should see all
> the values.
> 3- Now apply a FixedWindow... and then try and log the output.. the original
> elements wont appear, but the new OnTime generated ones will.
>
> Tested in Dataflow runner and things work ok, the direct runner fails.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
