1. a/b) No, they are deserialized into separate instances in any case
and are independent afterwards.
2. a/b) No, see 1).
3. a/b) No, as individual tasks are isolated by different class-loaders.
On 23/01/2020 09:25, M Singh wrote:
Thanks Yun for your answers.
By processor I did mean user def
Thanks Yun for your answers.
By processor I did mean user defined processor function. Keeping that in view,
do you have any advice on how the shared state - ie, the parameters passed to
the processor as mentioned above (not the key state or operator state) will be
affected in a distributed runt
Hi Mans
What's the meaning of 'processor' you defined here? A user defined function?
When talking about share state, I'm afraid it's not so easy to implement in
Flink. As no matter keyed state or operator state, they're both instantiated,
used and only thread-safe in operator scope. The only wa
