[
https://issues.apache.org/jira/browse/FLINK-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946896#comment-15946896
]
sunjincheng commented on FLINK-6204:
------------------------------------
[~shijinkui] thanks for pay attention on this. Actually I had left comments in
PR [#3386|https://github.com/apache/flink/pull/3386] [please
see|https://github.com/apache/flink/pull/3386#discussion_r107585318], I have
kept my point of view. The current master code is work well, but I personally
think that is not the best, I expect flink getting better, even if it is a
little bit of progress. Of course, I am very grateful to your proposal, we can
not waste the time of others. Anyway, thank you for expressing your opinion.
Thanks,
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)
