flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sunjincheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6204) Improve Event-Time OVER ROWS BETWEEN UNBOUNDED PRECEDING aggregation to SQL
Date Tue, 28 Mar 2017 13:02:41 GMT

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

sunjincheng commented on FLINK-6204:
------------------------------------

[~fhueske] is right´╝îlist does not ensure the failover but mechanism of timer can.

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

Mime
View raw message