Re: Making broadcast state queryable?

Thanks for the reply Oytun (and sorry for the late response, somehow just noticed). Requirement received, interesting one. Let's see whether this could draw any attention from the committers (smile). Best Regards, Yu On Fri, 6 Sep 2019 at 22:14, Oytun Tez wrote: > Hi Yu, > > Excuse my late

Re: Making broadcast state queryable?

Hi Yu, Excuse my late reply... We simply want Flink to be our centralized stream analysis platform, where we 1) consume data, 2) generate analysis, 3) present analysis. I honestly don't want "stream analysis" to spill out to other components in our ecosystem (e.g., sinking insights into a DB-like

Re: Making broadcast state queryable?

Good to know your thoughts and the coming talk in Flink Forward Berlin Oytun, interesting topic and great job! And it's great to hear the voice from application perspective. Could you share, if possible, the reason why you need to open the state to outside instead of writing the result to sink

Re: Making broadcast state queryable?

Thank you for the honest response, Yu! There is so much that comes to mind when we look at Flink as a "application framework" (my talk in Flink Forward in Berlin will be about

Re: Making broadcast state queryable?

Hi Oytun, Sorry but TBH such support will probably not be added in the foreseeable future due to lack of committer bandwidth (not only support queryable broadcast state but all about QueryableState module) as pointed out in other threads [1] [2]. However, I think you could open a JIRA for this