[jira] [Updated] (FLINK-13194) Add explicit clarification about thread-safety of state in document

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-13194:
-----------------------------------
    Labels: auto-deprioritized-major auto-unassigned pull-request-available stale-minor  (was: auto-deprioritized-major auto-unassigned pull-request-available)

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.


> Add explicit clarification about thread-safety of state in document
> -------------------------------------------------------------------
>
>                 Key: FLINK-13194
>                 URL: https://issues.apache.org/jira/browse/FLINK-13194
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Runtime / State Backends
>            Reporter: Yu Li
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned, pull-request-available, stale-minor
>
> Currently there's no explicit clarification about whether state is thread safe in our document meanwhile there are many user questions about this such as FLINK-13072, on [stackoverflow|https://stackoverflow.com/questions/55208345/flink-operator-state-is-thread-safe] and in [mailing list|https://s.apache.org/ya10u], and this JIRA aims at improving this.



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