Yes and no, I think state access is a valid use cases , and should surface in beam layer , through the sdk abstraction, or through a separate function like RichMapFunction of Flink. Hence the question.
Aparup On 7/26/16, 4:29 AM, "Aljoscha Krettek" <aljos...@apache.org> wrote: >Hi, >the purpose of Beam is to abstract the user from the underlying execution >engine. IMHO, allowing access to state of the underlying execution engine >will never be a goal for the Beam project. > >If you want/need to access Flink state, I think this is a good indicator >that you should use Flink directly because your programs would never run on >another runner anyways. > >Cheers, >Aljoscha > >On Mon, 25 Jul 2016 at 17:04 Aparup Banerjee (apbanerj) <apban...@cisco.com> >wrote: > >> I am looking for a way to access streaming engine state (Flink) in my beam >> transformations. I understand this can be accessed only though the runtime >> context. Has any one tried accessing flink runtime context in beam? May be >> roll it up as a custom API of some sort. Might need some changes in >> FlinkRunner is my hunch. >> >> Thanks, >> Aparup >>
