a FlinkSQL question: I'm running a simple test using the sql client (1.16.1): 1. I set a table with sequential data:

CREATE TABLE MyTable (
>    a bigint,
>    b int not null,
>    c varchar,
>    d timestamp(3)
> ) with ('connector' = 'datagen', 'rows-per-second' = '1', 'fields.a.kind' = 'sequence', 'fields.a.start' = '0', 'fields.a.end' = '1000000');

2. Then, I start a simple query on that table:

SELECT a FROM MyTable;

Which results in a constant flow of ever increasing integer values to be printed in the sql client. 3. The job shows up in the logs and the UI. I stop the job with a savepoint:

$ ./bin/flink stop --savepointPath ../1.16.1-savepoint <job-id>

This creates a savepoint and stops the job. 4. I want to restart the job from within the sql client:

SET 'execution.savepoint.path' = '<path-to-savepoint>';
SELECT a FROM MyTable;

--- My expectation would be that the sql client starts printing the incrementing number leaving the numbers out that were already printed in the run before the savepoint was created. But the sql client is not printing anything at all. With a more complex example, I actually see in the Flink UI that data is sent between the tasks. So, it's not that nothing is happening. But it seems like I'm missing something here 🤔