davidradl commented on code in PR #26249:
URL: https://github.com/apache/flink/pull/26249#discussion_r1983087489
##########
docs/content.zh/docs/learn-flink/streaming_analytics.md:
##########
@@ -83,7 +83,7 @@ Flink 中事件时间的处理取决于 *watermark 生成器*，后者将带有
<a name="latency-vs-completeness"></a>
### 延迟 VS 正确性
-watermarks
给了开发者流处理的一种选择，它们使开发人员在开发应用程序时可以控制延迟和完整性之间的权衡。与批处理不同，批处理中的奢侈之处在于可以在产生任何结果之前完全了解输入，而使用流式传输，我们不被允许等待所有的时间都产生了，才输出排序好的数据，这与流相违背。
+watermarks
给了开发者流处理的一种选择，它们使开发人员在开发应用程序时可以控制延迟和完整性之间的权衡。与批处理不同，批处理中的奢侈之处在于可以在产生任何结果之前完全了解输入，而使用流式传输，我们不被允许等待所有的数据都产生了，才输出排序好的数据，这与流相违背。
Review Comment:
From google translate the change it to wait for all the data from wait for
all the time, which seems reasonable.
At the end of this line I notice:
**The English:**
with streaming you must eventually stop waiting to see more of the input,
and produce some sort of result.
**The Chinese:**
we are not allowed to wait for all the data to be produced before outputting
the sorted data, which is contrary to the flow.
Please could you review this piece of the changed line as well, as the
meaning seems different to the English. This could be a quirk of google
translate but saying `you are not allowed to wait` - is not the same as the
English.
--
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
