Hi Hong, Given that this changes the REST API, which is a public interface, I'm wondering if this shouldn't first have had a (small) FLIP if I follow the guidelines from the overview page [1].
Best regards, Martijn [1] https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals On Mon, Jul 3, 2023 at 6:04 PM Teoh, Hong <lian...@amazon.co.uk.invalid> wrote: > Just adding the updates from the Slack thread - > @SamratDeb and @JulietLee have expressed interest, and there is a PR ready > for review! > https://github.com/apache/flink/pull/22901 > > Regards, > Hong > > > On 3 Jul 2023, at 16:56, Teoh, Hong <lian...@amazon.co.uk.INVALID> wrote: > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you can confirm the sender and know > the content is safe. > > > > Hi all, > > (This is a cross-post from a Slack message posted in #dev [1]. Posting > here for visibility) > > Recently I’ve been looking into improving the REST API that Flink has, to > make it more generally available for programmatic access (e.g. control > functions) rather than just for the Flink dashboard. > > In particular, various APIs seem to consume from the ExecutionGraph cache, > which is useful when displaying on a Flink dashboard (to guarantee > consistent behaviour), but since there is no way to “force” the latest > result, it might be not very useful for a control-function that wants to > retrieve the latest data. This could be achieved via Cache-Control HTTP > headers, as mentioned on this thread [2]. > > Looking for any contributors / committers who are interested in working on > these items together! (To bounce ideas / deliver this faster) > > > [1] https://apache-flink.slack.com/archives/C03GV7L3G2C/p1688051972688149 > [2] https://lists.apache.org/thread/7o330hfyoqqkkrfhtvz3kp448jcspjrm > > > > Regards, > Hong > > >
