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/projects/flink/flink-docs-release-1.0/apis/streaming/savepoints.html#changes-to-your-program Stephan On Mon, Apr 18, 2016 at 5:43 PM, Ufuk Celebi <u...@apache.org> wrote: > Can you please share the program before and after the savepoint? > > – Ufuk > > On Mon, Apr 18, 2016 at 3:11 PM, Ozan DENİZ <ozande...@outlook.com> 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 savepoint > <JobId>" command while the application is running. > > > > After saving snapshot of application, I canceled the job from web ui > than I changed the topology of Flink application. > > (To change the topology, I split the keyedstream into two seperate > keyedstream) > > > > After changing the topology, I run the new application by using the > snapshot which I took in first step. > > > > But after running the application, the window which has been snapshot, > triggers without the new log. > > > > Question is: Is there any way to save old window state to continue after > starting new topology with snapshot? > > >
