How to set fix JobId for my application.

[shashank734]

How I can set Fixed JobId for my flink Job. Cause queryable client required
Job ID. So whenever I'll update or redeploy my queryable state job than
JobID will change and i have to change and redeploy in queryable client app.

Is there any way I can fix the jobID or dynamically pass in the client app.



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

[Gary Yao-2]

Hi,

AFAIK it is not possible to set the job id manually.

You could get the job id via the REST API. For example,
http://host:port/joboverview/running gives you a list of running jobs [1] which
you can filter by name. Would that work for you?

Best,
Gary

[1] https://ci.apache.org/projects/flink/flink-docs-release-1.4/monitoring/rest_api.html#overview-of-jobs

On Thu, May 3, 2018 at 9:23 AM, shashank734 <[hidden email]> wrote:

How I can set Fixed JobId for my flink Job. Cause queryable client required
Job ID. So whenever I'll update or redeploy my queryable state job than
JobID will change and i have to change and redeploy in queryable client app.

Is there any way I can fix the jobID or dynamically pass in the client app.



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

[shashank734]

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/

[Gary Yao-2]

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 <[hidden email]> 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/

[shashank734]

Thanks for suggestion now using Kafka for information sharing between apps.



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/