Hi,
I gave some answers in the other mail thread. Some additional comment:
In general I think even configuration can be considered as state in this
case. If state is not set, the job can be considered as a fresh start.
Once the state is set, it would basically be just a configuration
update. You could set timers to periodically query either an external
service or just a distributed file system for an updated version of the
configuration.
If you want to avoid excessive state access, you could also cache the
state's content in a transient variable.
Regards,
Timo
On 16.12.20 21:50, vishalovercome wrote:
Will this work - In main method, serialize config into a string and store it
using ParameterTool with key as taskName and value as config (serialized as
string). Then in the open method, lookup the relevant configuration using
getTaskName().
A follow up to this would be configuring custom windowing functions. I have
a size as well as a time based window class where size and time limits are
configurable and passed as constructor arguments. How to change this
configuration when state persistence/recovery is enabled? A window doesn't
have an open method per se
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
