Re: Full Checkpoint information in UI and API

Hi Ryan, +1 for the name "incremental". Just had a look at the PR and looks like it has a compile error [1]. Additionally if it's possible it would be good to add some automated test. [1] https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=64974&view=logs&j=52b61abe-a3cc-5bde-c

Re: Full Checkpoint information in UI and API

Hi, I've updated the PR [https://github.com/apache/flink/pull/25899] to follow the incremental recommendation. It is short a test or two but otherwise should be ready to review. Ryan van Huuksloot Sr. Production Engineer | Streaming Platform [image: Shopify]

Re: Full Checkpoint information in UI and API

Hi, I would +1 for this. As for the name: incremental: true vs. false sounds good to me, which is aligned with the config name 'execution.checkpointing.incremental'. Best, Zakelly On Tue, Dec 17, 2024 at 12:01 PM Ryan van Huuksloot wrote: > Hello, > > Would the community be open to adding ad

Full Checkpoint information in UI and API

Hello, Would the community be open to adding additional information about the SNAPSHOT_TYPE to the Flink UI? Currently, you can tell if you have an aligned or unaligned checkpoint, savepoint or sync savepoint. You can infer incremental vs full checkpoints but it would be nice to expose it in the