Re: Managed Keyed state update

2018-08-14 Thread Fabian Hueske
gust 13, 2018 4:33 PM > *To:* Alexey Trenikhun > *Cc:* user@flink.apache.org > *Subject:* Re: Managed Keyed state update > > Hi, Alexey: > It depends on the state backend you use. If you use heap memory backend, > then you don't need to do put again. > However, if you use ro

Re: Managed Keyed state update

2018-08-13 Thread Alexey Trenikhun
Clear. Thank you Get Outlook for iOS<https://aka.ms/o0ukef> From: Renjie Liu Sent: Monday, August 13, 2018 4:33 PM To: Alexey Trenikhun Cc: user@flink.apache.org Subject: Re: Managed Keyed state update Hi, Alexey: It depends on the state backend you use.

Re: Managed Keyed state update

2018-08-13 Thread Renjie Liu
Hi, Alexey: It depends on the state backend you use. If you use heap memory backend, then you don't need to do put again. However, if you use rocksdb state backend, then you need to do the put again so that it will be saved by the checkpoint. On Tue, Aug 14, 2018 at 4:58 AM Alexey Trenikhun wrote

Managed Keyed state update

2018-08-13 Thread Alexey Trenikhun
Let’s say I have Managed Keyed state - MapState> x, I initialize for state for “k0” - x.put(“k0”, new Tuple2<>(“a”, “b”)); Later I retried state Tuple2 v = x.get(“k0”); and change value: v.f0=“U”;, does it make state ‘dirty’? In other words, do I need to call x.put(“k0”, v) again or change will