ldn't trigger and shouldn't call apply
> function.
>
> But when I checked the output file, I saw that window has been triggered
> just after I re-run the application with new topology.
>
> I think it flushes the old window.
>
> Is there any way to hold old window state
e, I saw that window has been triggered just
after I re-run the application with new topology.
I think it flushes the old window.
Is there any way to hold old window state and continue with coming log?
> Date: Mon, 18 Apr 2016 18:04:50 +0200
> Subject: Re: Savepoint for time windows
>
Hi!
Yes, window contents is part of savepoints. If you change the topology, it
is crucial that the new topology matches the old window contents to the new
operator.
If you change the structure of the program, you probably need to assign
persistent names to the operators. See
https://ci.apache.org
Can you please share the program before and after the savepoint?
– Ufuk
On Mon, Apr 18, 2016 at 3:11 PM, Ozan DENİZ wrote:
> Hi everyone,
>
> I am trying to implement savepoint mechanism for my Flink project.
>
> Here is the scenario:
>
> I got the snapshot of Flink application by using "flink s
Hi everyone,
I am trying to implement savepoint mechanism for my Flink project.
Here is the scenario:
I got the snapshot of Flink application by using "flink savepoint "
command while the application is running.
After saving snapshot of application, I canceled the job from web ui than I
cha
