Re: Initial value of ValueStates of primitive types

2018-08-17 Thread Averell
Thank you Dominik. So there's an implicit conversion, which means that getState().value() would always give a deteministic result (i.e: Boolean value would always be false, Int value would always be 0) I found another funny thing is even with ref type like Integer, there is also that implicit con

Re: Initial value of ValueStates of primitive types

2018-08-17 Thread Dominik WosiƄski
Hey, After you call, by default values you mean after you call : getRuntimeContext.getState() If so, the default value will be state with *value() *of null, as described in : /** * Returns the current value for the state. When the state is not * partitioned the returned value is the same for

Initial value of ValueStates of primitive types

2018-08-17 Thread Averell
Hi, In Flink's documents, I couldn't find any example that uses primitive type when working with States. What would be the initial value of a ValueState of type Int/Boolean/...? The same question apply for MapValueState like [String, Int] Thanks and regards, Averell -- Sent from: http://apach