[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-5572:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> 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: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)