Hi Ryan,
Just a quick note, the FLIP has been updated to reflect the latest changes in the Job UI and Job REST API. Thanks, Yi At 2025-09-26 11:31:28, "Yi Zhang" <[email protected]> wrote: >Hi Ryan, > > >Yes, that's a great point. The plan is to have each job link back to its >parent application in the Job UI for easier navigation. >And I agree, the UI can definitely be polished over time. Thanks again! > > >Best, >Yi > >At 2025-09-26 06:13:15, "Ryan van Huuksloot" ><[email protected]> wrote: >>Hi Yi, >> >>For the UI, I can see reasons to keep the Jobs tab as well. Will each job >>be also inversely associated with an Application in the Job UI? >> >>It is definitely not a blocker and something that can evolve over time as >>more people get exposed to this experience. >> >>Ryan van Huuksloot >>Staff Engineer, Infrastructure | Streaming Platform >>[image: Shopify] >><https://www.shopify.com/?utm_medium=salessignatures&utm_source=hs_email> >> >> >>On Thu, Sep 25, 2025 at 5:32 AM Lei Yang <[email protected]> wrote: >> >>> Hi Yi, thanks for creating this FLIP! >>> >>> I'm trying to understand your FLIP. By introducing the Application entity, >>> you're able to organically organize jobs, making them easier to observe >>> and manage. This is great work! >>> >>> I'd like to share some questions with you, and hope you could help me >>> clarify them: >>> >>> 1. When an application is in the FAILING state, how are the jobs that have >>> already reached the FINISHED state handled? Will they simply be ignored, >>> or will there be other actions taken? >>> >>> 2. In the "Follow-up Tasks", you mentioned high availability for the >>> application, >>> which will restart failed jobs to restore the application. However, I >>> didn't see the >>> description of the application's status during such restarts in the FLIP. I >>> think >>> we might need to introduce a RESTARTING status to explicitly indicate the >>> application is in the process of restarting? >>> >>> Best, >>> Lei >>> >>> Yi Zhang <[email protected]> 于2025年9月23日周二 11:24写道： >>> >>> > Hi everyone, >>> > >>> > >>> > I would like to start a discussion about FLIP-549: Support Application >>> > Management [1]. >>> > >>> > >>> > Despite Flink’s widespread adoption, the existing model for running user >>> > logic limits observability and execution flexibility, which affects user >>> > experience. This FLIP introduces a new application management framework >>> > designed to close these gaps and provide a foundation for future >>> > improvements. >>> > >>> > >>> > Looking forward to your feedback and suggestions. >>> > >>> > >>> > >>> > [1] >>> > >>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-549%3A+Support+Application+Management >>> > >>> > >>> > Best regards, >>> > >>> > Yi Zhang >>>
