Hi Max, state (keyed or operator state) is always local to the task. By default it is not accessible (read or write) from the outside or other tasks of the application.
You can expose keyed state as queryable state [1] to perform key look ups. This feature was designed for external application to access the state of Flink applications. However, that should also work from inside the same job. Best, Fabian [1] https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/stream/queryable_state.html 2017-11-30 6:01 GMT+01:00 m@xi <makisnt...@gmail.com>: > Hello everyone! > > I want to implement a streaming algorithm like Misa-Gries or Space Saving > in > Flink. The goal is to maintain the heavy hitters for my (possibly > unbounded) > input streams throughout all the time my app runs. More precisely, I want > to > have a non-stop running task that runs the Space Saving algorithm and > updates a data structure that should be accessible by other tasks like map, > flatmap of my Flink application at ad-hoc times. Although I am not so sure > of how I can achieve the aforementioned goal. > > First is it possible to have a structure in my main function that is > updated > by a task at all times and to be also accesible by others transformations > at > ad-hoc times?? > > Any ideas on how I can implement the above are more than welcome. > > Thanks in advance. > > Best, > Max > > > > -- > Sent from: http://apache-flink-user-mailing-list-archive.2336050. > n4.nabble.com/ >
