davidradl commented on code in PR #29269:
URL: https://github.com/apache/flink/pull/29269#discussion_r4083008752
##########
docs/content.zh/docs/dev/table/functions/ptfs.md:
##########
@@ -712,31 +712,84 @@ class CountingFunction extends
ProcessTableFunction<String> {
Flink's state backends provide different types of state to efficiently handle
large state.
-Currently, PTFs support three types of state:
+Currently, PTFs support the following types of state:
-- **Value state**: Represents a single value.
-- **List state**: Represents a list of values, supporting operations like
appending, removing, and iterating.
-- **Map state**: Represents a map (key-value pair) for efficient lookups,
modifications, and removal of individual entries.
+- **Eager value state**: Represents a single value that follows a
Read-Modify-Write cycle.
+- **Value view**: Represents a single value with lazy access.
+- **List view**: Represents a list of values, supporting operations like
appending, removing, and iterating.
Review Comment:
does it make sense to eager and lazy versions for lists and maps? If not it
would be worth mentioning how these concepts apply (or not) to the collections.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
