The problem is that `RichAsyncFunction` is allowed to trigger an asynchronous operation which can keep a reference to the `RuntimeContext`. However, it is not guaranteed when this operation is actually executed. Due to this, the underlying key could have changed, thus, accessing state which can belong to another key. One would have to reset the corresponding key before accessing the state. But this is not yet happening.
Cheers, Till On Fri, Oct 19, 2018 at 8:37 AM shimin yang <ysmcl...@gmail.com> wrote: > Hi all, > > Regarding to the RichAsyncFunction, why we cannot access the state through > runtime context like other operators? > > Best, > Shimin Yang >
