[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
[ 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)
[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
[ 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 stale-minor (was: auto-deprioritized-major) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or 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: Minor > Labels: auto-deprioritized-major, stale-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)
[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
[ https://issues.apache.org/jira/browse/FLINK-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5572: -- Priority: Minor (was: Major) > 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: Minor > Labels: auto-deprioritized-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)
[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
[ 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 (was: stale-major) > 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: auto-deprioritized-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)
[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
[ https://issues.apache.org/jira/browse/FLINK-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-5572: -- Labels: stale-major (was: ) > 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)
[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
[ https://issues.apache.org/jira/browse/FLINK-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shijinkui updated FLINK-5572: - Affects Version/s: (was: 1.1.4) (was: 1.2.0) 1.2.1 > 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.1 > 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)
[jira] [Updated] (FLINK-5572) ListState in SlidingEventTimeWindow and SlidingProcessingTimeWindow optimization
[ https://issues.apache.org/jira/browse/FLINK-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Syinchwun Leo updated FLINK-5572: - Description: 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? was: 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, shown as the following Fig. 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? > 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)
