You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "gaofeilong (Jira)" <ji...@apache.org> on 2019/09/21 11:36:00 UTC

[jira] [Commented] (FLINK-14161) wrong description of state

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

gaofeilong commented on FLINK-14161:
------------------------------------

this problem can be assigned to me.

> wrong description of state
> --------------------------
>
>                 Key: FLINK-14161
>                 URL: https://issues.apache.org/jira/browse/FLINK-14161
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: gaofeilong
>            Priority: Minor
>
> I don't think the description of the ValueState in the [https://github.com/apache/flink/blob/master/docs/getting-started/walkthroughs/datastream_api.zh.md] is right.
> I think It shoud be
>  
> {code:java}
> Modifications to the object returned by ValueState#valueare not guaranteed to be recognized by the system, and so all changes must be performed with ValueState#update. In this way, fault tolerance is managed automatically by Flink under the hood, and so you can interact with it like with any standard variable.
> {code}
>  
> Instead of 
> {code:java}
> Modifications to the object returned by ValueState#valueare not guaranteed to be recognized by the system, and so all changes must be performed with ValueState#update. Otherwise, fault tolerance is managed automatically by Flink under the hood, and so you can interact with it like with any standard variable.
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)