Hi Dawid -
I’m pretty keen on keeping it alive. Do we have a sense of what it would take
to get it “to a production ready state?”
Thanks!
Ron
> On Feb 4, 2022, at 5:06 AM, Dawid Wysakowicz wrote:
>
> Hi Karthik,
>
> The reason we deprecated it is because we lacked committers who could spend
*From: *Jatti, Karthik
*Date: *Friday, February 11, 2022 at 6:00 PM
*To: *Frank Dekervel , user@flink.apache.org
, dwysakow...@apache.org
*Subject: *Re: Queryable State Deprecation
Thank you Frank and Dawid for providing the context here.
*From: *Frank Dekervel
*Date: *Friday, February
anything that would look like
an obvious case.
Thanks,
Karthik
From: Jatti, Karthik
Date: Friday, February 11, 2022 at 6:00 PM
To: Frank Dekervel , user@flink.apache.org
, dwysakow...@apache.org
Subject: Re: Queryable State Deprecation
Thank you Frank and Dawid for providing the context here
Thank you Frank and Dawid for providing the context here.
From: Frank Dekervel
Date: Friday, February 4, 2022 at 9:56 AM
To: user@flink.apache.org
Subject: Re: Queryable State Deprecation
EXTERNAL SENDER
Hello,
To give an extra datapoint: after a not so
Hello,
To give an extra datapoint: after a not so successful experiment with
faust-streaming we moved our application to flink. Since flinks
queryable state was apparently stagnant, we implemented what was needed
to sink the state to an external data store for querying.
However, if queryabl
Hi Karthik,
The reason we deprecated it is because we lacked committers who could
spend time on getting the Queryable state to a production ready state. I
might be speaking for myself here, but I think the main use case for the
queryable state is to have an insight into the current state of th
Hi,
I see on the Flink Roadmap that Queryable state API is scheduled to be
deprecated but I couldn’t find much information on confluence or this mailing
group’s archives to understand the background as to why it’s being deprecated
and what would be a an alternative. Any pointers to help me get
