flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6204) Update all OVER window ProcessFunction implementations to use the SortedQueueState
Date Fri, 14 Jul 2017 09:45:00 GMT

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

Fabian Hueske commented on FLINK-6204:
--------------------------------------

I just created FLINK-7193 as a follow-up for this one (together with FLINK-6219) and will
close this issue.

[~sunjincheng121], can you please close your PR [#3630|https://github.com/apache/flink/pull/3630]
as well?
Thanks

>  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)

Mime
View raw message