[FLINK-17312] Support sql client start with restore savepoint

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.10.0, 1.11.0
• Component/s: Table SQL / Client
• Labels: pull-request-available
• Flags: Important
• Assignee: Unassigned
• Reporter: lun zhang
• Created: 22/Apr/20 02:42
• Updated: 08/Oct/21 09:48
• Resolved: 01/Jul/20 15:43

Description

Now flink support stop or cancel a flink job by flink cancel -s savepointpath . And you can restart the jar flink job from flink run -s savepointpath .

But in sql client, we can't specific the restart savepoint .

By help of ykt836 and lzljs3620320 we have two way to go.

1. the most easy way, set in envirment.yml. I've pull a request for it.It's  add restore-savepoint-path prop in Excution part.You can set restore-savepoint-path in envirment.yml or just in command line( by set execution.restore-savepoint-path=xxx). When we update a "insert" DML.It'll add restore-savepoint-path in job graph.And restart with the last restore-savepoint.But in this way we can only unset execution.restore-savepoint-path when you update two or more insert DML. 
2. support by DML hit(for eg: "insert into tb select * from tb2 with (restore-savepoint-path = 'xxx')". It's very useful if you want insert two or more DML in one sql client session. But It's may token more work to go.We need support a new DML hit.

In my opinion, the way 2 is most elegant to go.But it'll take much more working on it.Restart two or more stop with savepoint job is not usual in real world.So it's better to just add this in envirment variable.When we submit our job only need check the env variable and set the restore-savepoint in job graph.

Issue Links

• is related to: FLINK-16534 Support specify savepoint path when submitting sql job through sql client
• links to: GitHub Pull Request #11849
• links to: pull request