Hi Folks, I just wanted to double check, if there is any way to expose rest APIs using Flink sql tables ?
Thank you. On Thu, Jun 30, 2022 at 12:15 PM Yuan Mei <yuanmei.w...@gmail.com> wrote: > That's definitely something we want to achieve in the future term, and > your input is very valuable. > > One problem with the current queryable state setup is that the service is > bounded to the life cycle of Flink Job, which limits the usage of the state > store/service. > > Thanks for your insights. > > Best > Yuan > > On Wed, Jun 29, 2022 at 3:41 PM laxmi narayan <nit.dgp...@gmail.com> > wrote: > >> >> Hi Hangxiang, >> >> I was thinking , since we already store entire state in the checkpoint >> dir so why can't we expose it as a service through the Flink queryable >> state, in this way I can easily avoid introducing a cache and serve >> realtime APIs via this state itself and I can go to the database for the >> historical data. >> >> >> >> Thank you. >> >> >> On Wed, Jun 29, 2022 at 11:17 AM Hangxiang Yu <master...@gmail.com> >> wrote: >> >>> Hi, laxmi. >>> There are two ways that users can access the state store currently: >>> 1. Queryable state [1] which you could access states in runtime. >>> 2. State Processor API [2] which you could access states (snapshot) >>> offline. >>> >>> But we have marked the Queryable state as "Reaching End-of-Life". >>> We are also trying to find a graceful and effective way for users to >>> debug and troubleshoot. >>> So could you share your case about what you want to use it for ? >>> Your feedback is important for us to design it in the long term. Thanks! >>> >>> [1] >>> https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/fault-tolerance/queryable_state/ >>> [2] >>> https://nightlies.apache.org/flink/flink-docs-master/docs/libs/state_processor_api/ >>> [3] https://flink.apache.org/roadmap.html >>> >>> Best, >>> Hangxiang. >>> >>> On Tue, Jun 28, 2022 at 8:26 PM laxmi narayan <nit.dgp...@gmail.com> >>> wrote: >>> >>>> Hi Team, >>>> I am not sure if this is the right use case for the state-store but I >>>> wanted to serve the APIs using queryable-state, what are the different ways >>>> to achieve this ? >>>> >>>> I have come across a version where we can use Job_Id to connect to the >>>> state, but is there any other way to expose a specific rest-endpoint etc ? >>>> >>>> Any sample example/github link would be nice. >>>> >>>> >>>> >>>> Thank you. >>>> >>>
