You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/18 00:02:26 UTC

[jira] [Commented] (APEXMALHAR-2359) Optimise fire trigger to avoid go through all data

    [ https://issues.apache.org/jira/browse/APEXMALHAR-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15827092#comment-15827092 ] 

ASF GitHub Bot commented on APEXMALHAR-2359:
--------------------------------------------

Github user brightchen closed the pull request at:

    https://github.com/apache/apex-malhar/pull/518


> Optimise fire trigger to avoid go through all data
> --------------------------------------------------
>
>                 Key: APEXMALHAR-2359
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2359
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: bright chen
>            Assignee: bright chen
>   Original Estimate: 144h
>  Remaining Estimate: 144h
>
> KeyedWindowedOperatorImpl.fireNormalTrigger(Window, boolean) currently go through each window and key to check value. The data collection could be very huge as the discard period could be relative long time. If fireOnlyUpdatedPanes is false probably there don't have much space to improve. But if fireOnlyUpdatedPanes is true, we don't have to go through the whole data collection. We only need to go through the window and key which handle after last trigger.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)