You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Huang Xingbo (Jira)" <ji...@apache.org> on 2020/12/25 02:05:00 UTC
[jira] [Commented] (FLINK-20756) PythonCalcSplitConditionRule is
not working as expected
[ https://issues.apache.org/jira/browse/FLINK-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254702#comment-17254702 ]
Huang Xingbo commented on FLINK-20756:
--------------------------------------
[~zhongwei] Thanks a lot for reporting this issue. I will look into it asap
> 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
> Priority: Major
>
> 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)