GitHub user sangkyoonnam added a comment to the discussion: Planning Flink Agents 1.0 - Brainstorming
Thanks. I'll open an issue to let users set a stable operator UID through both the Java and Python agent APIs. Without an explicit UID, Flink derives the operator ID from the stream topology, and some topology changes can alter it. For an agent operator without one, `KafkaActionStateCleanupTool plan` currently requires `--operator-uid-hash` to read its recovery markers from a snapshot. I'd also like to take #1332 for the cross-release test setup and its first at-rest scenario, then follow up here with a design and restore scenarios for pending actions and events. Could you assign #1332 to me? GitHub link: https://github.com/apache/flink-agents/discussions/1327#discussioncomment-19234761 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
