You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/01 23:29:00 UTC
[jira] [Updated] (FLINK-18060) Add notice for heap-based state
backend of state access reference problem
[ https://issues.apache.org/jira/browse/FLINK-18060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-18060:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
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 Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> Add notice for heap-based state backend of state access reference problem
> -------------------------------------------------------------------------
>
> Key: FLINK-18060
> URL: https://issues.apache.org/jira/browse/FLINK-18060
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 1.10.1
> Reporter: Yun Tang
> Priority: Major
> Labels: auto-unassigned, stale-major
> Fix For: 1.14.0
>
>
> Currently, when talking about the limitation of {{MemoryStateBackend}} and {{FsStateBackend}} in [documentation|https://ci.apache.org/projects/flink/flink-docs-stable/ops/state/state_backends.html#the-memorystatebackend], Flink only focus on the memory checkpoint size limit. However, current documentation forgets to talk about the reference problem, which added in {{CopyOnWriteStateMap}}:
> {noformat}
> IMPORTANT: the contracts for this class rely on the user not holding any references to objects returned by this map beyond the life cycle of per-element operations. Or phrased differently, all get-update-put operations on a mapping should be within one call of processElement. Otherwise, the user must take care of taking deep copies, e.g. for caching purposes.
> {noformat}
> This actually also applies to {{NestedStateMap}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)