Thanks David for the feedback!
> CheckpointStatsCache is also populated using the "cached execution graph,"
> so there is nothing to gain from the "staleness" pov; see
> AbstractCheckpointHandler for more details.
You are right about the CheckpointStatisticsCache. Sorry I was referring to the
Hi Hong,
Thanks for starting the discussion.
seems to be using the cached version of the entire Execution graph (stale
> data), when it could just use the CheckpointStatsCache directly
CheckpointStatsCache is also populated using the "cached execution graph,"
so there is nothing to gain from
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
