Expected Behavior
Core should submit the jar to the flink cluster and then the subprocess should terminate, instead of following the job to completion.
Current Behavior
Running a job using the FlinkRunner is a blocking call that runs indefinitely (streaming) or until completion (batch)
Steps to reproduce
- Run a job on a flink cluster
Possible Solution
Should follow the same process as DataflowRunner: submit job -> return job id -> allow the jobmanager to keep track of status of the job
We do need to retrieve the Flink job id from the Flink cluster in that case.
Expected Behavior
Core should submit the jar to the flink cluster and then the subprocess should terminate, instead of following the job to completion.
Current Behavior
Running a job using the
FlinkRunneris a blocking call that runs indefinitely (streaming) or until completion (batch)Steps to reproduce
Possible Solution
Should follow the same process as DataflowRunner: submit job -> return job id -> allow the jobmanager to keep track of status of the job
We do need to retrieve the Flink job id from the Flink cluster in that case.