Hi all, Currently, the most convenient way of programmatically submitting a job to a running session cluster is using Flink’s RestClusterClient. Unfortunately, it is only supported, as of now, to submit a job graph.[1] To construct a job graph from a jar file, additional Flink dependencies are required, which is not ideal.
It is also possible to directly use the Flink rest API and first upload the jar file via /jars/upload[2] and then run it via /jar/:jarId/run[3]. It has the downside that it is impossible to set a Flink execution configuration, and it will always take the underlying session cluster configuration. I know changing the ClusterClient has already been discussed. It would involve a lot of effort, so what do you think of making the jar execution more prominent via the rest endpoint by adding the option to pass an execution configuration? Best, Fabian [1] https://github.com/apache/flink/blob/65cd385d7de504a946b17193aceea73b3c8e78a8/flink-clients/src/main/java/org/apache/flink/client/program/ClusterClient.java#L95 [2] https://github.com/apache/flink/blob/c2972b6e336cc3b3a6cbd22c69a6710dab5246e6/flink-container/src/main/java/org/apache/flink/container/entrypoint/StandaloneApplicationClusterConfigurationParserFactory.java#L56 <https://github.com/apache/flink/blob/c2972b6e336cc3b3a6cbd22c69a6710dab5246e6/flink-container/src/main/java/org/apache/flink/container/entrypoint/StandaloneApplicationClusterConfigurationParserFactory.java#L56> [3] https://github.com/apache/flink/blob/c2972b6e336cc3b3a6cbd22c69a6710dab5246e6/flink-container/src/main/java/org/apache/flink/container/entrypoint/StandaloneApplicationClusterConfigurationParserFactory.java#L56
