[ 
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  
(was: auto-unassigned pull-request-available stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Major, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> 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
>
> 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.3.4#803005)

Reply via email to