[
https://issues.apache.org/jira/browse/FLINK-8477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16359841#comment-16359841
]
ASF GitHub Bot commented on FLINK-8477:
---------------------------------------
Github user Aitozi commented on the issue:
https://github.com/apache/flink/pull/5405
Hi @aljoscha , you have mentioned two points :
1. The events arrived may out of order in event-time processing
2. We can use windowFunction or ProcessWindowFunction to filter serverl
window by specify the start time of window and the endtime.
I have some differerent ideas:
1. when we deal with the out-of-order eventtime stream, we may specify the
maxOutOfOrder to avoid the too much late elements skipped, so when the job
restart/start the maxNumOfWindow to be skipped can be set to
maxOutOfOrder/(the length of the thumbling window), So that the late elements
will not produce incorrect results. The num of the window need to be skipped is
according to the degree of the out of order
2. We need to skip the serveral broken window data , and we dont know which
window is broken, we can just detect which window is first fired and the serval
window after this is broken too. The num should very from the production
(according to the maxOutOfOrder & the length of the window )
> Add api to support for user to skip the first incomplete window data
> --------------------------------------------------------------------
>
> Key: FLINK-8477
> URL: https://issues.apache.org/jira/browse/FLINK-8477
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Affects Versions: 1.4.0, 1.3.2
> Reporter: aitozi
> Assignee: aitozi
> Priority: Major
> Fix For: 1.4.2
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
