[ https://issues.apache.org/jira/browse/FLINK-14161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gaofeilong updated FLINK-14161: ------------------------------- Description: 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} was: I don't think the description of the ValueState in the [datastream_api document|[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} > 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)