[FLINK-37502][docs] Translate documentation for Disaggregated State Management into Chinese #26312
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
davidradl
reviewed
Mar 20, 2025
| @@ -497,6 +497,8 @@ In a typical stateful Flink Application you don't need operators state. It is | |||
| mostly a special type of state that is used in source/sink implementations and | |||
| scenarios where you don't have a key by which state can be partitioned. | |||
|
|
|||
| **Notes:** Operator state is still not supported in Python DataStream API. | |||
There was a problem hiding this comment.
nit: in Python -> in the Python
Zakelly
reviewed
Mar 31, 2025
docs/content.zh/docs/dev/datastream/fault-tolerance/state_v2.md
Outdated
Show resolved
Hide resolved
docs/content.zh/docs/dev/datastream/fault-tolerance/state_v2.md
Outdated
Show resolved
Hide resolved
| This is called the 'disaggregated state management'. For more information about this, | ||
| please see [Disaggregated State Management]({{< ref "docs/ops/state/disaggregated_state" >}}). | ||
| 新的 state API 比以前的 API 更灵活，用户可以通过新的 API 使用异步状态操作，这使得新的 API 更加强大有效。 | ||
| 异步 state 访问对“存算分离”来说是必要的，即令状态后端支持大状态和在必要时将文件溢出到远程文件系统的能力。更多关于 |
There was a problem hiding this comment.
Suggested change
| 异步 state 访问对“存算分离”来说是必要的，即令状态后端支持大状态和在必要时将文件溢出到远程文件系统的能力。更多关于 | |
| 异步 state 访问对存算分离来说是必要的，即令状态后端支持大状态时将文件溢出到远程文件系统的能力。更多关于 |
docs/content.zh/docs/dev/datastream/fault-tolerance/state_v2.md
Outdated
Show resolved
Hide resolved
| 和之前的 state API 不同，新的 state API 允许用户使用异步状态访问。每种类型的状态都提供了两种版本的 API：同步和异步。 | ||
| 同步 API 是一个阻塞等待状态访问完成的 API。异步 API 是非阻塞的，它会返回一个 `StateFuture`，这个 `StateFuture` 会在状态访问完成时完成。 | ||
| 在 `StateFuture` 完成时，callback 或者 后续逻辑将会被调用（如果有的话）。异步 API 比同步 API 更加高效，更推荐使用异步 API。 | ||
| 注意，**不建议**在同一个用户函数中混合使用同步和异步状态访问。 |
There was a problem hiding this comment.
Suggested change
| 注意，**不建议**在同一个用户函数中混合使用同步和异步状态访问。 | |
| 需要注意，**不建议**在同一个用户函数中混合使用同步和异步状态访问。 |
| 但两个`asyncGet`的完成顺序不能保证。因此，无法保证两个 `StateFuture` 后续步骤的执行顺序，即无法确定元素 A 和 元素 B 的 | ||
| `asyncClear` 和 `asyncUpdate` 的调用顺序。 | ||
|
|
||
| 尽管状态访问方法可能会乱序执行，这也不意味着所有用户代码会串行执行。在 `processElement`, `flatMap` 或者 `thenXXxx` |
There was a problem hiding this comment.
Suggested change
| 尽管状态访问方法可能会乱序执行，这也不意味着所有用户代码会串行执行。在 `processElement`, `flatMap` 或者 `thenXXxx` | |
| 尽管状态访问方法可能会乱序执行，这也不意味着所有用户代码会并行执行。在 `processElement`, `flatMap` 或者 `thenXXxx` |
docs/content.zh/docs/dev/datastream/fault-tolerance/state_v2.md
Outdated
Show resolved
Hide resolved
|
|
||
| 通常，您无需担心状态访问方法的执行顺序问题，但 Flink 仍确保一些规则: | ||
| * 同 key 的元素的执行顺序严格按照元素到达 `flatMap` 的顺序执行的。 | ||
| * 传递给 `thenXXxx` 方法的函数会按照调用链的顺序执行。如果它们不属于调用链，或者同时有多个调用链，则无法保证执行顺序。 |
There was a problem hiding this comment.
Suggested change
| * 传递给 `thenXXxx` 方法的函数会按照调用链的顺序执行。如果它们不属于调用链，或者同时有多个调用链，则无法保证执行顺序。 | |
| * 传递给 `thenXXxx` 方法的函数会按照调用链的顺序执行。如果同时有多个调用链，则无法保证执行顺序。 |
docs/content.zh/docs/dev/datastream/fault-tolerance/state_v2.md
Outdated
Show resolved
Hide resolved
docs/content.zh/docs/dev/datastream/fault-tolerance/state_v2.md
Outdated
Show resolved
Hide resolved
…anagement into Chinese
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
Chinese documents for Disaggregate State and new State APIs
Brief change log
Verifying this change
This change is a docs work without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation