Hi Dasraj,
Yes, I would recommend to use Public and, if necessary, PublicEvolving
APIs as they provide better guarantees for future maintenance.
Unfortunately there are no Docs about which APIs are public or
publiceEvolving but you can see the annotations of the classes in the
source code.
I guess
Hi Kostas,
I am trying to migrate our code base to use new ClusterClient method for job
submission.
As you recommending to use new publicEvolving APIs, any doc or link for
reference will be helpful.
Thanks,
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
Hi Dasraj,
You are right. On your previous email I did not pay attention that you
migrated from 1.9.
Since 1.9 the ClusterClient has changed significantly as it is not
annotated as @Public API.
I am not sure how easy it is to use the old logic in your settings.
You could try copying the old code
Hi Kostas,
ClusterClient class is not our custom class it is in
org.apache.flink.client.program package.
i can see defination of ClusterClient has changed from 1.9.2 to 1.11.1
https://ci.apache.org/projects/flink/flink-docs-release-1.9/api/java/org/apache/flink/client/program/ClusterClient.html
<
Hi Dasraj,
Could you please specify where is the clusterClient.run() method and
how does it submit a job to a cluster?
Is the clusterClient your custom code?
Any details will help us pin down the problem.
One thing that is worth looking at is the release-notes of 1.11 [1].
There you will find all
Hi,
Currently we are using Flink 1.9.2 in our project and we are submitting Job
from jar.
below is that code we are using currently for jobsubmission:
clusterClient.setDetached(true);
clusterClient.run(packagedProgram,
Integer.valueOf(params.get(Constants.PARAMS_PARALLELISM)));
After upgrading i
