[
https://issues.apache.org/jira/browse/FLINK-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945183#comment-15945183
]
sunjincheng commented on FLINK-6204:
------------------------------------
[~Yuhong_kyo] Actually just like I comment in FLINK-5658，At the tableAPI level,
I do not recommend using a memory data structure with a non-constant amount of
data. Using the runtime timer mechanism, you can optimize with the
framework-timer optimization, TableAPI can take full advantage of the runtime
mechanism, or even timer merge.
> 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)
