Re: state inside functions

[vishalovercome <vi...@moengage.com>]

When running in HA mode or taking savepoints, if we pass configuration as
constructor arguments, then it seems as though changing configuration at a
later time doesn't work as it uses state to restore older configuration. How
can we pass configuration while having the flexibility to change the values
at a later date?

I've started another discussion with many more questions -
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Changing-application-configuration-when-restoring-from-checkpoint-savepoint-tp40189.html



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

Re: state inside functions

[Timo Walther <tw...@apache.org>]

Hi,

if you would like to dynamically adjust configuration of your streaming 
job, it might be a good approach to consider the configuration as a 
stream itself.

The connect() API can be used to connect a main stream with a control 
stream. In any case the configuration should be persisted in state if it 
should be present after restore. Otherwise, you need to implement a 
logic where the operator must query the latest configuration from some 
external system which could become the bottleneck.

Regards,
Timo


On 16.12.20 22:07, vishalovercome wrote:
> When running in HA mode or taking savepoints, if we pass configuration as
> constructor arguments, then it seems as though changing configuration at a
> later time doesn't work as it uses state to restore older configuration. How
> can we pass configuration while having the flexibility to change the values
> at a later date?
> 
> I've started another discussion with many more questions -
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Changing-application-configuration-when-restoring-from-checkpoint-savepoint-tp40189.html
> 
> 
> 
> --
> Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
>