sangkyoonnam commented on issue #1192: URL: https://github.com/apache/flink-agents/issues/1192#issuecomment-6065950657
I'd like to take this one, following #1197 in the same #1055 set. The check would go in `RunnerContextImpl.sendEvent`, which every user emission reaches, Python included through `sendEventJson`. An event that arrives there with `upstreamEventId` or `upstreamActionName` set fails with an error that points to `attributes`. `ActionTask.finalizeOutputEvents` keeps binding lineage as it does today. Outputs restored from the action state and the operator's `AgentRunBeginEvent` don't go through `sendEvent`, so recovery and replay keep their identity and lineage. Python's `send_event` would run the same check before serializing, so the error names the Python field, and the frozen-ID error would mention `reconstruct_from`. An action that rebuilds a typed event with `fromEvent`/`reconstruct_from` and sends it carries the source's ID and lineage, so it is rejected too, and the docs would say that a new emission starts from a fresh event. Could you assign it 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]
