Hey Dan!
On Thu, Sep 29, 2016 at 10:58 PM, dan bress <danbr...@gmail.com> wrote:
> If I deploy a job to Flink called "A"(set my
> streamExecutionEnvironment.execute("A"), that checkpoints state. Then I
> cancel "A" and deploy the same job but call it "B", will it pick up A's
> state? Or is checkpointing key'd by the job name?
No, this will not happen at the moment. By default, checkpoints are
scoped to the job and cleaned up on cancellation. You would have to
trigger a savepoint [1] and then resume from that savepoint when
submitting B.
For Flink 1.2, there has just been created an issue [2] to introduce a
cancel variant that automatically triggers a savepoint before
cancelling the job. That will be a little more convenient.
[1] https://ci.apache.org/projects/flink/flink-docs-master/setup/savepoints.html
[2] https://issues.apache.org/jira/browse/FLINK-4717
> The reason I ask is I would like a way to reflect the version of the job
> that is deployed in the flink UI somewhere, so that I know what is
> running. I put this in the jobname as a quick fix, but I'm concerned it
> might affect checkpointing when I deploy a new version. Is there a good
> way to put the version of the job somewhere such that it gets reflected in
> the UI?
The job name is the only thing that comes to my mind.
Best,
Ufuk
