You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Hangxiang Yu (Jira)" <ji...@apache.org> on 2023/08/18 02:49:00 UTC

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

    [ https://issues.apache.org/jira/browse/FLINK-13194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755776#comment-17755776 ] 

Hangxiang Yu commented on FLINK-13194:
--------------------------------------

Hi, [~yunta] 
Kindly ping. Are you still working on this ? I think we could continue to improve this.

> 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: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, 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.20.10#820010)