Skip to content

[FLINK-37422][docs] Fix typos and translation alignment in streaming analytics zh document#28215

Open
arvindKandpal-ksolves wants to merge 2 commits into
apache:masterfrom
arvindKandpal-ksolves:FLINK-37422
Open

[FLINK-37422][docs] Fix typos and translation alignment in streaming analytics zh document#28215
arvindKandpal-ksolves wants to merge 2 commits into
apache:masterfrom
arvindKandpal-ksolves:FLINK-37422

Conversation

@arvindKandpal-ksolves
Copy link
Copy Markdown

What is the purpose of the change

This PR fixes multiple typos and translation alignments in the streaming analytics Chinese documentation.
Specifically, it addresses the issue raised in FLINK-37422 (and the previously closed stale PR #26249) where a literal translation created confusion, and it fixes an additional mistranslation on the same page.

Brief change log

Modified docs/content.zh/docs/learn-flink/streaming_analytics.md:

  • Line 86: Fixed the main typo by changing "所有的时间都产生了" (time) to "所有的数据都产生了" (data). This accurately reflects the English source ("stop waiting to see more of the input") and aligns with stream processing principles.
  • Line 183: Fixed an additional mistranslation by changing "(包括会话时间)" (session time) to "(包括会话窗口)" (session windows), matching the explicit term in the English documentation.

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): no
  • The public API, i.e., is any changed class annotated with @Public(Evolving): no
  • The serializers: no
  • The runtime per-record code paths (performance sensitive): no
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
  • The S3 file system connector: no

Documentation

  • Does this pull request introduce a new feature? no
  • If yes, how is the feature documented? not applicable

Was generative AI tooling used to co-author this PR?
  • Yes (Claude Code)

Generated-by: Claude Code

…analytics zh document

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@arvindKandpal-ksolves
Copy link
Copy Markdown
Author

Hi @davidradl , Please review this when you have a time.

@flinkbot
Copy link
Copy Markdown
Collaborator

flinkbot commented May 20, 2026

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

### 延迟 VS 正确性

watermarks 给了开发者流处理的一种选择,它们使开发人员在开发应用程序时可以控制延迟和完整性之间的权衡。与批处理不同,批处理中的奢侈之处在于可以在产生任何结果之前完全了解输入,而使用流式传输,我们不被允许等待所有的时间都产生了,才输出排序好的数据,这与流相违背。
watermarks 给了开发者流处理的一种选择,它们使开发人员在开发应用程序时可以控制延迟和完整性之间的权衡。与批处理不同,批处理中的奢侈之处在于可以在产生任何结果之前完全了解输入,而使用流式传输,我们不被允许等待所有的数据都产生了,才输出排序好的数据,这与流相违背。
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

它们使开发人员在开发应用程序时可以控制延迟和完整性之间的权衡 -> 它们使开发人员可以在延迟和完整性之间进行权衡

批处理中的奢侈之处在于可以在产生任何结果之前完全了解输入 -> 批处理可以在产生结果之前完全了解输入

而使用流式传输,我们不被允许等待所有的数据都产生了,才输出排序好的数据,这与流相违背 -> 流处理则需要及时的输出结果,而无法等待所有数据的到来

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @klion26 , I have update the commit , Please take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants