[ https://issues.apache.org/jira/browse/FLINK-27028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aitozi updated FLINK-27028: --------------------------- Description: The {{flink-kubernetes-operator}} is using the JarUpload + JarRun to support the session job submission. However, currently the RestClusterClient do not expose a way to upload the user jar to session cluster and trigger the jar run api. So a naked RestClient is used to achieve this, but it lacks the common retry logic. Can we expose these two api the the rest cluster client to make it more convenient to use in the operator was: The flink-kubernetes-operator is using the JarUpload + JarRun to support the session job management. However, currently the RestClusterClient do not expose a way to upload the user jar to session cluster and trigger the jar run api. So I used to naked RestClient to achieve this. Can we expose these two api the the rest cluster client to make it more convenient to use in the operator > Support to upload jar and run jar in RestClusterClient > ------------------------------------------------------ > > Key: FLINK-27028 > URL: https://issues.apache.org/jira/browse/FLINK-27028 > Project: Flink > Issue Type: Improvement > Components: Client / Job Submission > Reporter: Aitozi > Priority: Major > > The {{flink-kubernetes-operator}} is using the JarUpload + JarRun to support > the session job submission. However, currently the RestClusterClient do not > expose a way to upload the user jar to session cluster and trigger the jar > run api. So a naked RestClient is used to achieve this, but it lacks the > common retry logic. > Can we expose these two api the the rest cluster client to make it more > convenient to use in the operator -- This message was sent by Atlassian Jira (v8.20.1#820001)