Hi Martjin,
>
> For any extension on the SQL syntax, there should be a FLIP. I would like
> to understand how this works for both bounded and unbounded jobs, how this
> works with the SQL upgrade story. Could you create one?
Sure. I’m preparing one. Please give me the permission if possible.
My
Hi Paul,
For any extension on the SQL syntax, there should be a FLIP. I would like
to understand how this works for both bounded and unbounded jobs, how this
works with the SQL upgrade story. Could you create one?
I'm also copying in @Timo Walther and @Jark Wu
for their opinion on this.
Best r
Hi Martijn,
Thanks a lot for your input.
> Have you already thought on how you would implement this in Flink?
Yes, I roughly thought about the implementation:
1. Extending Executor to support job list via ClusterClient.
2. Extending Executor to support savepoint trigger/cancel/remove via JobCli
Hi Paul,
Thanks for opening the discussion. I agree that there are opportunities in
this area to increase user value.
I would say that the syntax should be part of a proposal in a FLIP, because
the implementation would actually be the complex part, not so much the
syntax :) Especially since this
Hi team,
Greetings from Apache Kyuubi(incubating) community. We’re integrating Flink as
a SQL engine and aiming to make it production-ready.
However, query/savepoint management is a crucial but missing part in Flink SQL,
thus we reach out to discuss the SQL syntax with Flink community.
We pr
