You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "xuyang (Jira)" <ji...@apache.org> on 2022/09/13 11:00:00 UTC
[jira] [Updated] (FLINK-29280) Join hint are not propagated in subquery
[ https://issues.apache.org/jira/browse/FLINK-29280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
xuyang updated FLINK-29280:
---------------------------
Summary: Join hint are not propagated in subquery (was: Join hint will not be propagated in subquery)
> Join hint are not propagated in subquery
> ----------------------------------------
>
> Key: FLINK-29280
> URL: https://issues.apache.org/jira/browse/FLINK-29280
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.16.0
> Reporter: xuyang
> Priority: Major
>
> Add the following code in JoinHintTestBase to re-produce this bug.
> {code:java}
> @Test
> public void testJoinHintWithJoinHintInSubQuery() {
> String sql =
> "select * from T1 WHERE a1 IN (select /*+ %s(T2) */ a2 from T2 join T3 on T2.a2 = T3.a3)";
> verifyRelPlanByCustom(String.format(sql, buildCaseSensitiveStr(getTestSingleJoinHint())));
> } {code}
> This is because that calcite will not propagate the hint in subquery and flink also doesn't resolve it in FlinkSubQueryRemoveRule
--
This message was sent by Atlassian Jira
(v8.20.10#820010)