[FLINK-17126] Correct the execution behavior of BatchTableEnvironment

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.11.0
• Component/s: Table SQL / API
• Labels: pull-request-available

Release Note

In previous versions, BatchTableEnvironment.execute() and ExecutionEnvironment.execute() can both trigger table and DataSet programs for legacy batch planner. Since 1.11.0, batch table programs can only be triggered by BatchEnvironment.execute(). Once table program is convereted into DataSet program (through toDataSet() method), it can only be triggered by ExecutionEnvironment.execute().

• Assignee: godfrey he
• Reporter: godfrey he
• Created: 14/Apr/20 04:10
• Updated: 10/Jun/20 09:31
• Resolved: 22/Apr/20 08:41

Description

This issue is similar to FLINK-16363.
In previous versions, BatchTableEnvironment.execute() can both trigger table and DataSet programs. Since 1.11.0, table programs can only be triggered by BatchTableEnvironment.execute(). Once table program is convereted into DataSet program (through toDataSet() method), it can only be triggered by ExecutionEnvironment.execute().

Issue Links

• blocks: FLINK-16367 Introduce createStatementSet method in TableEnvironment
• blocks: FLINK-17251 supports INSERT statement in TableEnvironment#executeSql and Table#executeInsert api
• blocks: FLINK-17267 supports EXPLAIN statement in TableEnvironment#executeSql and Table#explain api
• links to: GitHub Pull Request #11794