[jira] [Resolved] (FLINK-5151) Add discussion about object mutations to heap-based state backend docs.

["Yun Tang (Jira)" <ji...@apache.org>]

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

Yun Tang resolved FLINK-5151.
-----------------------------
    Fix Version/s: 1.16.0
                   1.14.5
       Resolution: Fixed

merged in master: 4175fefd557d30fcf065fc376bd8210c6ec598de
release-1.15: 3cdcbaf1fb874d751f3ae625cfebf67384a8abcb
release-1.14: a57e98dab03a81897f6f0c1807444ecabb92834a

> Add discussion about object mutations to heap-based state backend docs.
> -----------------------------------------------------------------------
>
>                 Key: FLINK-5151
>                 URL: https://issues.apache.org/jira/browse/FLINK-5151
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Runtime / State Backends
>    Affects Versions: 1.1.4, 1.2.0
>            Reporter: Fabian Hueske
>            Assignee: Hangxiang Yu
>            Priority: Major
>              Labels: auto-deprioritized-major, pull-request-available, stale-assigned
>             Fix For: 1.15.0, 1.16.0, 1.14.5
>
>
> Flink's heap state backends store data as objects on the heap. Any object mutations are hence reflected in the state.
> This can lead to unexpected behavior. For example, in case of sliding windows, multiple window hold references to the same object. Hence, all windows are affected if such an object is modified, e.g., by a {{WindowFunction}}, {{ReduceFunction}}, or {{FoldFunction}}, and might return invalid results.
> We should add this information to the state backend documentation and also point out that the RocksDB backend is not affected by this because all data is serialized.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)