Hi community,
Currently, HistoryServer supports only a quantity-based job archive retention policy [1]. This is insufficient for scenarios such as: - Time-based retention (e.g., last X days). - Combined rules (e.g., within 7 days AND ≤100 jobs). To address these limitations, I’d like to start a discussion on FLIP-490 [2], which proposes a more flexible job archive retention mechanism that supports time-based, quantity-based, and composite strategies (with AND/OR logic). Looking forward to your feedback. Best, Yuepeng Pan [1] https://github.com/apache/flink/blob/cae5fb4d3b6d9e0c10c3539ea4994fc1ad463b70/flink-runtime-web/src/main/java/org/apache/flink/runtime/webmonitor/history/HistoryServer.java#L241 [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=332499857
