gyfora opened a new pull request, #29216:
URL: https://github.com/apache/flink/pull/29216
## What is the purpose of the change
The state catalog (introduced in FLINK-40176) lets you query
savepoint/checkpoint state via SQL, but so far only covered keyed state. This
PR extends it to non-keyed (operator) state — `ListState`, `UnionState`, and
`BroadcastState` — exposing each as its own table.
## Brief change log
- Extract non-keyed state schema info (value/key type, LIST vs UNION vs
BROADCAST) from the operator state serialization proxy, tolerating missing POJO
classes the same way keyed state does
- Build `CatalogTable`s for `ListState`/`UnionState` (one row per element)
and `BroadcastState` (one row per map entry, keyed on `map_key`)
- Wire the new table kinds into `StateCatalog` (naming/listing) and
`SavepointDynamicTableSourceFactory` (scan)
- Add integration tests reading back list/union/broadcast state, including
POJO value types with the class missing from the classpath
## Verifying this change
This change added tests and can be verified as follows:
- Added `StateCatalogNonKeyedITCase` (run against both HashMap and RocksDB
state backends), covering all three state shapes and the missing-POJO-class
fallback path
## 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)`: yes (`StateCatalog`, still `@PublicEvolving`)
- 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? yes
- If yes, how is the feature documented? JavaDocs
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Code (Sonnet 5)
--
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]
