DanielLeens commented on issue #11351: URL: https://github.com/apache/seatunnel/issues/11351#issuecomment-5148481030
Thanks for opening the STIP/design PR in #11612. That is the right first step for this feature. A runtime execution graph should not start as a UI-only patch, because the useful part is the data contract: which existing realtime metrics and job state signals are reused, how node and edge status are derived, what large-DAG degradation looks like, and how the graph avoids adding expensive new polling paths. I would keep the first PR focused on that contract and validation plan. The implementation can follow after reviewers agree on the graph payload shape, refresh behavior, and fallback behavior for large or partially unavailable runtime data. -- 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]
