Thanks Rong, I have made some quick test changing the SQL select (adding a select field in the middle) and reran the job from a savepoint and it worked without any errors. I want to make sure i understand how at what point the state is stored and how does it work.
Let's simplify the scenario and forget my specific case of dynamically generated pojo. let's focus on generic steps of: Source->register table->SQL select and group by session->retracted stream (Row)->transformToPojo (Custom Map function) ->pushToSink And let's assume the SQL select is changed (a field is added somewhere in the middle of the select field). So: We had intermediate results that are in the old format that are loaded from state to the new Row object in the retracted stream. is that an accurate statement? at what operator/format is the state stored in this case? is it the SQL result/Row? is it the Pojo? as this scenario does not fail for me im trying to understand how/where it is handled in Flink? -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
