davidradl commented on code in PR #26393:
URL: https://github.com/apache/flink/pull/26393#discussion_r2026671289


##########
docs/content/docs/libs/state_processor_api.md:
##########
@@ -515,6 +515,28 @@ Before you interrogate state using the table API, make 
sure to review our [Flink
 
 IMPORTANT NOTE: State Table API only supports keyed state.
 
+### Metadata
+
+The SQL connector allows users to read metadata of savepoints in the following 
way:
+```SQL
+LOAD MODULE state;
+SELECT * FROM savepoint_metadata('/root/dir/of/checkpoint-data/chk-1');
+```
+
+The table have the following fixed schema:
+
+| Key                                      | Data type       | Description     
                                                                 |
+|------------------------------------------|-----------------|----------------------------------------------------------------------------------|
+| checkpoint-id                            | BIGINT NOT NULL | Checkpoint ID.  
                                                                 |
+| operator-name                            | STRING          | Operator Name.  
                                                                 |
+| operator-uid                             | STRING          | Operator UID.   
                                                                 |
+| operator-uid-hash                        | STRING NOT NULL | Operator UID 
hash.                                                               |
+| operator-parallelism                     | INT NOT NULL    | Parallelism of 
the operator.                                                     |
+| operator-max-parallelism                 | INT NOT NULL    | Maximum 
parallelism of the operator.                                             |
+| operator-subtask-state-count             | INT NOT NULL    | Number of 
operator subtask states.                                               |

Review Comment:
   It looks like a good addition to me



-- 
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]

Reply via email to