You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2017/07/14 09:46:00 UTC
[jira] [Closed] (FLINK-6204) Update all OVER window
ProcessFunction implementations to use the SortedQueueState
[ https://issues.apache.org/jira/browse/FLINK-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabian Hueske closed FLINK-6204.
--------------------------------
Resolution: Won't Fix
Closed in favor of FLINK-7193 and FLINK-6219.
> Update all OVER window ProcessFunction implementations to use the SortedQueueState
> -----------------------------------------------------------------------------------
>
> Key: FLINK-6204
> URL: https://issues.apache.org/jira/browse/FLINK-6204
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: sunjincheng
> Assignee: sunjincheng
>
> Currently `event time OVER ROWS BETWEEN UNBOUNDED PRECEDING aggregation to SQL` implementation class: ` UnboundedEventTimeOverProcessFunction` use data size uncontrollable memory data structures`sortedTimestamps: util.LinkedList [Long] cache data timestamps and sort timestamps. IMO,It's not a good way, because in the production environment there are millions of window data pre millisecond in our application scenario.So, I want to remove `util.LinkedList [Long] `. Welcome anyone to give me feedback.
> What do you think? [~fhueske] and [~Yuhong_kyo]
> When a SortedQueueState is available, we will Update all OVER window ProcessFunction implementations to use the SortedQueueState.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)