Hi Lei,
Thank you for the feedback! The "Archiving Directory Structure" section describes a change in how archived files are organized under jobmanager.archive.fs.dir. While this change was originally proposed in FLIP-549, it's indeed a significant application-level update, so I'm glad to have the chance to clarify it here. To answer your question directly: backward compatibility is fully preserved. In earlier Flink versions, job archives were written directly under the configured jobmanager.archive.fs.dir. With this update, Flink will instead use a hierarchical cluster-application-job structure. We understand that many users already have archives stored in the legacy flat layout. To ensure a smooth transition, the History Server will be updated to read archives from both the old and new directory structures. As a result, all previously archived jobs will remain accessible and visible. If you have additional questions or specific edge cases in mind, I’d be happy to discuss them further! Best, Yi At 2025-12-24 11:35:00, "Lei Yang" <[email protected]> wrote: >Hi Yi, > >Thank you for creating this FLIP! The introduction of the Application >entity significantly enhances the observability and manageability of >user logic, especially benefiting batch workloads. This is truly >excellent work! > >However, I have a compatibility concern and would appreciate your >clarification. In the “Archiving Directory Structure” section, I noticed >that the directory structure has been changed. If users have configured >a persistent external path for jobmanager.archive.fs.dir, will their >existing archives become unreadable after this change? Will the >implementation of this FLIP maintain backward compatibility with >previously archived job data? > >Best regards, >Lei > >Yi Zhang <[email protected]> 于2025年12月17日周三 14:18写道： > >> Hi everyone, >> >> I would like to start a discussion about FLIP-560: Application Capability >> Enhancement [1]. >> >> The primary goal of this FLIP is to improve the usability and availability >> of Flink applications >> >> by introducing the following enhancements: >> >> >> >> 1. Support multi-job execution in Application Mode, which is an important >> batch-processing use case. >> 2. Support re-running the user's main method after JobManager restarts due >> to failures in Session Mode. >> 3. Expose exceptions thrown in the user's main method via REST/UI. >> >> >> >> Looking forward to your feedback and suggestions! >> >> >> >> [1] >> >> https://cwiki.apache.org/confluence/display/FLINK/FLIP-560%3A+Application+Capability+Enhancement >> >> >> >> Best Regards, >> >> Yi Zhang
