Hello team, I was reading through the documentation and I have a doubt, does the table API & SQL can use or needs operators IDs for better management of savepointing ? As this piece of the documentation mentions they are highly recommended for savepointing, but I only found it for DataStream API, not for Table API & SQL. So I wonder if in Table & SQL it makes sense to do savepoints, after all they can window the stream, group, join streams right? If it makes sense to do savepoints in table api & sql would there be a way to give operator IDs? This is an extract from the documentation:

Assigning Operator IDs
It is highly recommended that you specify operator IDs via the uid(String) method. These IDs are used to scope the state of each operator.

DataStream<String> stream = env.
  // Stateful source (e.g. Kafka) with ID
  .addSource(new StatefulSource())
  .uid("source-id") // ID for the source operator
  .shuffle()
  // Stateful mapper with ID
  .map(new StatefulMapper())
  .uid("mapper-id") // ID for the mapper
  // Stateless printing sink
  .print(); // Auto-generated ID

Hello Eugenio, I am also facing same issue, if you got any suggestions meanwhile please share with us too, thank you.