I am not sure that this is impossible, but it is not the use case queryable state was designed for. I don't know the details of your application, but you could try to merge the updating and the querying operators into a single one.
You could connect two streams with connect() and use a keyed CoProcessFunction. This will have the advantages that all state access are local. Cheers, Fabian 2017-07-31 13:24 GMT+02:00 Biplob Biswas <revolutioni...@gmail.com>: > Hi Fabian, > > I read about the process function and it seems a perfect fit for my > requirement. Although while reading more about queryable-state I found that > its not meant to do lookups within job (Your comment in the following > link). > > http://apache-flink-user-mailing-list-archive.2336050. > n4.nabble.com/Best-practices-to-maintain-reference-data- > for-Flink-Jobs-td13215.html#a13233 > > The thing is I wanted to maintain a local state store which is queryable > within the same job such that one operator creates and updates it and then > another operator queries the store based on a given key. > > I was hoping this to be possible but it seems not to be the case, can you > shed some light and if possible recommend some alternatives? > > Regards, > Biplob > > > > -- > View this message in context: http://apache-flink-user- > mailing-list-archive.2336050.n4.nabble.com/Flink- > QueryableState-with-Sliding-Window-on-RocksDB-tp14514p14555.html > Sent from the Apache Flink User Mailing List archive. mailing list archive > at Nabble.com. >
