[
https://issues.apache.org/jira/browse/FLINK-36715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004354#comment-18004354
]
Sergey Nuyanzin commented on FLINK-36715:
-----------------------------------------
[~au_miner] are you sure?
In order to reproduce it you first need to drop RexUtil from Flink repo which
is currently a WA for this
I don't know what kind of join you use in your test (broadcast, shuffle,
nestedloop, etc...)
the test you can use to reproduce (after RexUtil removal)
{{org.apache.flink.table.planner.plan.batch.sql.join.JoinTestBase#testInnerJoinWithJoinConditionPushDown}}
(there are also others)
> Changed behavior for filter push down for IS NOT DISTINCT FROM after Calcite
> upgrade to 1.33
> ---------------------------------------------------------------------------------------------
>
> Key: FLINK-36715
> URL: https://issues.apache.org/jira/browse/FLINK-36715
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API, Table SQL / Planner
> Reporter: Sergey Nuyanzin
> Priority: Major
>
> After moving to 1.33 need to put RexUtil into Filnk repo to prevent a number
> of failures (more than 30)
> like
> {noformat}
> FlinkLogicalCalc(select=[CAST(0:BIGINT AS BIGINT) AS k, v, k AS k0, v0])
> +- FlinkLogicalJoin(condition=[true], joinType=[left])
> :- FlinkLogicalCalc(select=[v], where=[=(k, 0:BIGINT)])
> : +- FlinkLogicalLegacyTableSourceScan(table=[[default_catalog,
> default_database, src, source: [TestTableSource(k, v)]]], fields=[k, v])
> +- FlinkLogicalValues(type=[RecordType(BIGINT k, VARCHAR(2147483647) v)],
> tuples=[[]])
> This exception indicates that the query uses an unsupported SQL feature.
> Please check the documentation for the set of currently supported SQL
> features.
> {noformat}
> This is a result of https://issues.apache.org/jira/browse/CALCITE-5336
> the jira issue is to adapt Flink behavior and to remove RexUtil after that
> from Flink repo
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
