[
https://issues.apache.org/jira/browse/FLINK-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537048#comment-16537048
]
ASF GitHub Bot commented on FLINK-9687:
---------------------------------------
Github user Aitozi commented on the issue:
https://github.com/apache/flink/pull/6224
Hi, @aljoscha
I read the PR of https://issues.apache.org/jira/browse/FLINK-5363, i think
it is not a same thing with this PR. You meant to get `TriggerResult` no matter
the window content is empty or not. And I meant to check the `TriggerResult`
first to avoid get window state when the trigger are not ready to `FIRE`. And I
think the cost of get window state is much more cost, so i think we can get the
triggerResult first.
> Delay the state fetch only when the triggerResult is fire
> ---------------------------------------------------------
>
> Key: FLINK-9687
> URL: https://issues.apache.org/jira/browse/FLINK-9687
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 1.5.0
> Reporter: aitozi
> Assignee: aitozi
> Priority: Major
> Labels: pull-request-available
>
> When the window operator is fired by the event timer or processing timer, it
> fetch the state content first. I think it only need to fetch the content from
> windowState when the triggerResult is Fire. So we have to change the order to
> avoid this cost ( the cost of fetch content from state is more than judge the
> triggerResult).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
