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
