[FLINK-20756] PythonCalcSplitConditionRule is not working as expected

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.1, 1.13.0
• Component/s: API / Python
• Labels: pull-request-available
• Assignee: Huang Xingbo
• Reporter: Wei Zhong
• Created: 24/Dec/20 02:39
• Updated: 28/May/21 06:57
• Resolved: 28/Dec/20 09:52

Description

Currently if users write such a SQL:

`SELECT pyFunc5(f0, f1) FROM (SELECT e.f0, e.f1 FROM (SELECT pyFunc5(a) as e FROM MyTable) where e.f0 is NULL)`

It will be optimized to:

`FlinkLogicalCalc(select=[pyFunc5(pyFunc5(a)) AS f0])
+- FlinkLogicalCalc(select=[a], where=[IS NULL(pyFunc5(a).f0)])
+- FlinkLogicalLegacyTableSourceScan(table=[[default_catalog, default_database, MyTable, source: [TestTableSource(a, b, c, d)]]], fields=[a, b, c, d])`

The optimized plan is not runnable, we need to fix this.

Issue Links

• links to: GitHub Pull Request #14492
• links to: GitHub Pull Request #14505