Hi Yi, Thanks for the excellent work on this FLIP. Formalizing the Application concept is a huge step forward, and it will definitely make the History Server more intuitive for batch jobs.
I was thinking through the follow-up tasks and had a couple of long-term questions. First, on Application HA: making env.execute() idempotent is the right goal. My question is about the scope - is the vision to also help users manage stateful logic in their main() with its external side effects, or is the focus for now just on the Flink job submission part? My other question is about the History Server. The new API is great for the UI, but how should automated tools handle fast lookups via /jobs/:jobid? I'm just wondering if the expectation is that operators will need to build their own index to maintain performance for that critical use case. Overall, this is a great proposal that addresses some very real pain points. +1 Thanks, Kartikey On Tue, Sep 23, 2025 at 8:54 AM Yi Zhang <[email protected]> wrote: > 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
