[
https://issues.apache.org/jira/browse/FLINK-5151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5151:
----------------------------------
Labels: auto-deprioritized-major stale-assigned (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 issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> 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: Minor
> Labels: auto-deprioritized-major, stale-assigned
> Fix For: 1.15.0
>
>
> 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)
