You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2019/10/18 11:59:00 UTC

[jira] [Closed] (FLINK-7684) Avoid multiple data copies in MergingWindowSet

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

Aljoscha Krettek closed FLINK-7684.
-----------------------------------
    Resolution: Abandoned

I'm closing this as "Abandoned", since there is no more activity and the code base has moved on quite a bit. Please re-open this if you feel otherwise and work should continue.

> Avoid multiple data copies in MergingWindowSet
> ----------------------------------------------
>
>                 Key: FLINK-7684
>                 URL: https://issues.apache.org/jira/browse/FLINK-7684
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>    Affects Versions: 1.2.0, 1.2.1, 1.3.0, 1.3.1, 1.3.2
>            Reporter: Piotr Nowojski
>            Assignee: Piotr Nowojski
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently MergingWindowSet uses ListState of tuples to persists it's mapping. This is inefficient because this ListState of tuples must be converted to a HashMap on each access.
> Furthermore, for some cases it might be inefficient to check whether mapping has changed before saving it on state.
> Those two issues are causing multiple data copies and constructing multiple Lists/Maps per each processed element, which is a reason for noticeable performance issues.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)