You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "shijinkui (JIRA)" <ji...@apache.org> on 2017/01/25 15:41:26 UTC
[jira] [Commented] (FLINK-5572) ListState in SlidingEventTimeWindow
and SlidingProcessingTimeWindow optimization
[ https://issues.apache.org/jira/browse/FLINK-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837925#comment-15837925 ]
shijinkui commented on FLINK-5572:
----------------------------------
IMO, this proposal will save several times' memory. Syinchwun Leo have some demo to implements it. The result effect is perfect.
I think we can improve ListState with the everybody's suggestion.
> ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
> --------------------------------------------------------------------------------
>
> Key: FLINK-5572
> URL: https://issues.apache.org/jira/browse/FLINK-5572
> Project: Flink
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.0, 1.1.4
> Environment: CentOS 7.2
> Reporter: Syinchwun Leo
>
> When using ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow, an element may be assigned to multiple overlapped windows. It may lead to storage consuming. for example,
> window(SlidingEventTimeWindows.of(Time.seconds(10), Time.seconds(2))).apply(UDF window function), each element is assigned to 5 windows, When the window size is very large, it is unacceptable(size/slide is very large).
> We plan to make a little optimization, and the doc is in
> https://docs.google.com/document/d/1HCt1Si3YNGFwsl2H5SO0f7WD69DdBBPVJA6abd3oFWo/edit?usp=sharing
> Comments?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)