DanielLeens commented on issue #11668: URL: https://github.com/apache/seatunnel/issues/11668#issuecomment-5229109810
This looks like a larger design topic rather than a single standalone feature request, and I think the umbrella framing is useful here. What makes this worth keeping as an umbrella is that the cross-cutting questions are real and should not be re-decided independently in seven separate issues: 1. which observability data is already available server-side versus what would require new engine-side state; 2. what refresh cadence and retention cost are acceptable for UI consumers; 3. which frontend building blocks should be shared across the job graph, metrics, checkpoint, and worker-level views. From the proposal, the overall problem statement is clear: Zeta already has meaningful runtime data, but it is fragmented across APIs and not surfaced in a coherent operator workflow yet. The next step that would make this much easier for the community to review is to turn this umbrella into a coordination anchor with explicit boundaries: - what belongs in this umbrella versus in the child issues; - which contracts must stay consistent across #11351, #11352, #11353, #10750, #11665, #11666, and #11667; - which parts are pure UI composition versus which parts need new engine or REST contracts. I would keep the individual implementation work in the child issues, but use this umbrella to converge on the shared design decisions first. That should reduce duplicated review churn and make multi-contributor progress much easier. -- 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]
