Hi Juan,
usually the Flink operators contain the optimized expression that was
defined in SQL. You can also name the the entire job using
env.execute("Your Name") if that would help to identify the query.
Regarding checkpoints, it depends how you define "small changes". You
must ensure that the execution plan (Flink operator structure) remain
unchanged. So it is no problem to change scalar functions calls or
change values of literals. But you should not change return types
between operations.
I think we will have an additional page in the docs about that soon.
Regards,
Timo
Am 2/27/18 um 2:26 PM schrieb Juan Gentile:
Hello,
We are currently testing the SQL API using 1.4.0 version of Flink and
we would like to know if it’s possible to name a query or parts of it
so we can easily recognize what it’s doing when we run it.
An additional question is, In case of small changes done to the
query/ies, and assuming we are using checkpoints, how will it restore
the state of it/them when we re-deploy?
Thank you,
Juan G.
