Hi, Weizheng
> 在 2020年8月13日,19:44,Danny Chan 写道:
>
> tEnv.executeSql would execute the SQL asynchronously, e.g. submitting a job
> to the backend cluster with a builtin job name
`tEnv.executeSql` is an asynchronous method which will submit the job
immediately. If you’re test in your IDE, yo
Weighing ~
tEnv.executeSql would execute the SQL asynchronously, e.g. submitting a job to
the backend cluster with a builtin job name, the tEnv.executeSql itself did
return a JobResult immediately with a constant affected rows count -1.
Best,
Danny Chan
在 2020年8月13日 +0800 PM3:46,Lu Weizheng ,写道
Thanks Timo,
So no need to use execute() method in Flink SQL If I do all the thins from
source to sink in SQL.
Best Regards,
Lu
> 2020年8月13日 下午3:41,Timo Walther 写道:
>
> Hi Lu,
>
> `env.execute("table api");` is not necessary after FLIP-84 [1]. Every method
> that has `execute` in its name w
Hi Lu,
`env.execute("table api");` is not necessary after FLIP-84 [1]. Every
method that has `execute` in its name will immediately execute a job.
Therefore your `env.execute` has an empty pipeline.
Regards,
Timo
[1]
https://wiki.apache.org/confluence/pages/viewpage.action?pageId=134745878