[
https://issues.apache.org/jira/browse/FLINK-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948373#comment-15948373
]
sunjincheng commented on FLINK-6204:
------------------------------------
Hi [~Yuhong_kyo], I once again considered LinkedList, the most fundamental need
is that we need a sortedStateBackEnd, if we add a sorted state backend, such as
(sortedMapState), we can naturally delete the LinkedList, So temporary use
LinkedList Is also possible. I think you can go ahead in
[FLINK-6200|https://issues.apache.org/jira/browse/FLINK-6200] What do you
think? [~Yuhong_kyo]
Best,
SunJincheng
> Improve Event-Time OVER ROWS BETWEEN UNBOUNDED PRECEDING aggregation to SQL
> ---------------------------------------------------------------------------
>
> Key: FLINK-6204
> URL: https://issues.apache.org/jira/browse/FLINK-6204
> Project: Flink
> Issue Type: Bug
> 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]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
