Hi, Julian. Thank you for the information. I also want to know that
:
1. If the final sql is converted to the sub-query, Does it mean that
there exist a conversion rule (Join) ?
2. Will there be other built-in rules cause this result besides
JoinConditionPushRule ?
------------------ ???????? ------------------
??????:
"dev"
<[email protected]>;
????????: 2021??10??12??(??????) ????3:34
??????: "dev"<[email protected]>;
????: Re: Disable the subquery
Have you considered disabling JoinConditionPushRule?
> On Oct 12, 2021, at 12:26 AM, JiaTao Tao <[email protected]> wrote:
>
> Do you use the RelToSqlConverter to convert plan to sql?
>
> Regards!
>
> Aron Tao
>
>
> luoc <[email protected]> ??2021??10??11?????? ????4:30??????
>
>> Hello Calcite team,
>>
>>
>> &nbsp; I am going to develop a new feature on my project with the
Calcite.
>> But got the following issues :
>>
>>
>> Input SQL :
>>
>>
>> SELECT A.N_NAME, B.R_NAME FROM V1.NATION A LEFT JOIN V1.REGION B ON
>> A.N_REGIONKEY = B.R_REGIONKEY WHERE B.R_NAME = 'ASIA';
>>
>>
>> Actual SQL (send to DB) :
>>
>>
>> SELECT "NATION0"."N_NAME" AS "n_name", "t"."R_NAME" AS "r_name"
>> FROM "V1"."NATION" AS "NATION0"
>> INNER JOIN (SELECT *
>> FROM "V1"."REGION"
>> WHERE "R_NAME" = 'ASIA') AS "t" ON "NATION0"."N_REGIONKEY" =
>> "t"."R_REGIONKEY";
>>
>>
>> If possible, How can I disable the join auto-convert to the subquery
>> syntax? Because the backend DB does not support the subquery (but the
`left
>> join` is supported). Add the specified rule or rewrite the
`JdbcJoinRule`
>> class ?
>>
>>
>> Thanks for your time.
