Hi, If I understand correctly, you are using Queryable State to access state of one job from another one. To avoid redeployment, some operator in application B would need to regularly poll the REST API to discover changes of the job id of application A. It is doable but not advised to use Queryable State to share information between Flink jobs. Alternatively, you can write out the information from application A to one or multiple data sinks and consume these from application B.
Best, Gary On Thu, May 3, 2018 at 8:21 PM, shashank734 <shashank...@gmail.com> wrote: > Thanks for the response, Actually I know that. The main thing I have to use > that job id of app A in the queryable state in other application B. In that > case, I don't want to redeploy application B whenever I change something in > application A. > > > > > > -- > Sent from: http://apache-flink-user-mailing-list-archive.2336050. > n4.nabble.com/ >
