liboshuai01 commented on code in PR #25624:
URL: https://github.com/apache/flink/pull/25624#discussion_r1838352255
##########
docs/content.zh/docs/dev/datastream/operators/process_function.md:
##########
@@ -26,68 +26,61 @@ under the License.
# Process Function
-## The ProcessFunction
+## ProcessFunction 简介
Review Comment:
已采纳，并修改。
##########
docs/content.zh/docs/dev/datastream/operators/process_function.md:
##########
@@ -338,17 +331,14 @@ if __name__ == '__main__':
{{< hint warning >}}
-Before Flink 1.4.0, when called from a processing-time timer, the
`ProcessFunction.onTimer()` method sets
-the current processing time as event-time timestamp. This behavior is very
subtle and might not be noticed by users. Well, it's
-harmful because processing-time timestamps are indeterministic and not aligned
with watermarks. Besides, user-implemented logic
-depends on this wrong timestamp highly likely is unintendedly faulty. So we've
decided to fix it. Upon upgrading to 1.4.0, Flink jobs
-that are using this incorrect event-time timestamp will fail, and users should
adapt their jobs to the correct logic.
+在 Flink 1.4.0 之前，在调用处理时间定时器时，`ProcessFunction.onTimer()`
方法将当前的处理时间设置为事件时间的时间戳。此行为非常不明显，用户可能不会注意到。
+然而，这样做是有害的，因为处理时间的时间戳是不确定的，并且和 watermark 不一致。此外，用户依赖于此错误的时间戳来实现逻辑很有可能导致非预期的错误。
+因此，我们决定对其进行修复。在 1.4.0 后，使用此错误的事件时间时间戳的 Flink 作业将失败，用户应将其作业更正为正确的逻辑。
{{< /hint >}}
-## The KeyedProcessFunction
+## KeyedProcessFunction 简介
Review Comment:
已采纳，并修改。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
