Hi Ron, thanks you for sharing your use case and your initiative to save Queryable State. Queryable State was deprecated due to a lack of maintainers and thus the community did not have resources to improve and develop it further. The deprecation notice was added to signal this lack of attention to our users. On the other hand, I am not aware of anyone who is actively working towards actually dropping Queryable State. So, I don't think this will happen anytime soon.
Personally, I see a lot of potential in Queryable State, but to make it really, really useful it still needs a lot of work and the current architecture/implementation might need to be re-thought from scratch in my opinion. In that case, the current implementation might need to phased out again, but opposed to today there would be an alternative then. I am not aware of anyone at Immerok who currently has time to review & support a major effort in this direction. Just keeping the current implementation alive without any fundamental changes might not be too much work, though. So, all in all, I think, Queryable State will neither be fundamentally improved nor dropped any time soon. If you are committed to maintaining the current implementation of Queryable State in terms of addressing bugs, test instabilities and potentially small features requests, I am +1 to remove it from the deprecation list again provided that we keep the APIs @Experimental. Cheers, Konstantin Am Mo., 29. Aug. 2022 um 01:30 Uhr schrieb Ron Crocker <rcroc...@newrelic.com.invalid>: > Hi - > > For those of you who didn’t see my talk from Flink Forward, here’s a link < > https://www.slideshare.net/FlinkForward/using-queryable-state-for-fun-and-profit> > to the slides. > By implementing the ideas first brought forward in the blog post < > https://www.ververica.com/blog/queryable-state-use-case-demo>, we’ve > found we can save a pretty substantial amount of expense using Flink > Queryable State as a replacement for certain off-board caches. > > Given that, I’m quite keen on rescuing queryable state from deprecation. > However, I’m not at all sure how to start that conversation (other than by > just starting it). > > I believe my argument for rescuing this feature is supported in my talk, > though I’m open to further discussion. > > Perhaps the next thing to understanding is why, in concrete terms, > queryable state was added to the deprecation list. Can someone enlighten me > on that? > > Ron > — > Ron Crocker > New Relic Fellow & Architect > ( ( •)) New Relic > rcroc...@newrelic.com > M: +1 630 363 8835 > > -- https://twitter.com/snntrable https://github.com/knaufk
