Hi all, I have been looking at the Flink REST API implementation, and had some question on potential improvements. Looking to gather some thoughts:
1. Only use what is necessary. The GET /checkpoints API seems to be using the cached version of the entire Execution graph (stale data), when it could just use the CheckpointStatsCache directly. I am thinking of doing this refactoring. Anyone aware of a reason we don’t do this already? 2. Configuration for web.refresh-interval controls both dashboard refresh rate and ExecutionGraph cache. I am thinking of introducing a new configuration, rest.cache.timeout 3. Cache-Control on the HTTP headers. Seems like we are using caches in our REST endpoint. It would be step in the right direction to introduce cache-control in our REST API headers, so that we can improve the programmatic access of the Flink REST API. Looking forwards to hearing people’s thoughts. Regards, Hong
