[
https://issues.apache.org/jira/browse/FLINK-9687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537042#comment-16537042
]
ASF GitHub Bot commented on FLINK-9687:
---------------------------------------
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/6224
I think the reasons at that time where:
- it changes the semantics of Triggers
- You can get into a situation where you call `Trigger.onEventTime()`, the
`Trigger` returns `FIRE` or `FIRE_AND_PURGE`, and then you don't actually have
any window contents to emit
> 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)
