[
https://issues.apache.org/jira/browse/FLINK-17312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091310#comment-17091310
]
lun zhang commented on FLINK-17312:
-----------------------------------
Thanks for your replay.I have build a `sql client` python program where you
can write and manage your `flink sql`. You can see more in my github project
[fsqlfly|[https://github.com/mrzhangboss/fsqlfly]] .Now I'm ready for use it
in really world .
But I found a missing significant future in `sql client`. You can stop with
savepoint in `sql client` by running `flink stop -s savepoint jobid`. But we
can't use this `savepoint` in `sql client` command line. So I pull a request
add `savepoint` support in yml file. like
envirment.yml
{{execution:}}
{{ planner}}{{: blink}}
{{ type: streaming}}
{{ savepoint-path: hdfs:///tmp/savepoints/jasdf # the location of you latest
stoppoint file}}
{{}}
By support this future.This will help `sql client` build a high availability
`sql job`. I'm already tests my code in `flink-1.10`.It's very helpful when you
can stop and restart you `sql job` by savepoint.
> Support sql client savepoint
> ----------------------------
>
> Key: FLINK-17312
> URL: https://issues.apache.org/jira/browse/FLINK-17312
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Client
> Affects Versions: 1.10.0, 1.11.0
> Reporter: lun zhang
> Priority: Major
> Labels: pull-request-available
>
> Sql client not support sql job savepoint current. It's important when you
> use this in really world.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
