[jira] [Updated] (FLINK-20756) PythonCalcSplitConditionRule is not working as expected

["Xintong Song (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xintong Song updated FLINK-20756:
---------------------------------
    Fix Version/s:     (was: 1.12.2)
                   1.12.1

> PythonCalcSplitConditionRule is not working as expected
> -------------------------------------------------------
>
>                 Key: FLINK-20756
>                 URL: https://issues.apache.org/jira/browse/FLINK-20756
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Python
>            Reporter: Wei Zhong
>            Assignee: Huang Xingbo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0, 1.12.1
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)