[
https://issues.apache.org/jira/browse/FLINK-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328841#comment-17328841
]
Flink Jira Bot commented on FLINK-5572:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow
> optimization
> --------------------------------------------------------------------------------
>
> Key: FLINK-5572
> URL: https://issues.apache.org/jira/browse/FLINK-5572
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Affects Versions: 1.2.1
> Environment: CentOS 7.2
> Reporter: Syinchwun Leo
> Priority: Major
> Labels: stale-major
>
> 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
(v8.3.4#803005)
