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 you have access to the source code given that previously you were using the cluster client directly.
You can always of course use Flink's REST API [1] to submit a job, which provides stability guarantees. If you want to risk a bit more, you can check the PipelineExecutors in the codebase to see how job submission is currently done within Flink. This will give you some ideas I hope about how to proceed. I hope this helps, Kostas [1]https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/rest_api.html On Fri, Aug 7, 2020 at 8:07 AM dasraj <raj-kumar-...@microfocus.com> wrote: > > 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/
