We're doing a stream.keyBy().window().aggregate() to aggregate customer feedback into sessions. Every now and then we have to update the job, e.g. change the key, so that we can't easlily continue from the previous state.
Cancelling the job (without restarting from last savepoint) will result in loosing ongoing sessions. So we typically go back a few hours when we restart to minimize the loss. Is there any way of making the job flush it's content (sessions) on job cancellation? That will result in splitting ongoing sessions in two, which is perfectly fine for our purpose. Any thoughts ? Lars
