Will env.execute() and executeInsert() submit 2 jobs?

[HaochengWang]

My program firstly did something on a data stream using DataStream API, and then I converted it into a table and inserted it into another table for sink, at the end I wrote  ‘env.execute(‘jobname’)’ to make sure the DataStream API part work.

But I found the job will create 2 Flink job, and from the name of each, I know 1 is for the “Insert” and 1 for the DataStream job.

Should I delete ‘env.execute(‘jobname’)’ to reduce the superfluous job?

[Yik San Chan]

I believe you should delete. You can delete that and see if that reduces the extra job.

On Wed, Apr 7, 2021 at 5:02 PM 王 浩成 <[hidden email]> wrote:

My program firstly did something on a data stream using DataStream API, and then I converted it into a table and inserted it into another table for sink, at the end I wrote  ‘env.execute(‘jobname’)’ to make sure the DataStream API part work.

But I found the job will create 2 Flink job, and from the name of each, I know 1 is for the “Insert” and 1 for the DataStream job.

Should I delete ‘env.execute(‘jobname’)’ to reduce the superfluous job?