You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Vladimir Steshin (Jira)" <ji...@apache.org> on 2023/08/20 10:38:00 UTC

[jira] [Closed] (CALCITE-5945) Forced join order SQL hint.

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

Vladimir Steshin closed CALCITE-5945.
-------------------------------------
    Resolution: Won't Fix

Wrong project.

> Forced join order SQL hint.
> ---------------------------
>
>                 Key: CALCITE-5945
>                 URL: https://issues.apache.org/jira/browse/CALCITE-5945
>             Project: Calcite
>          Issue Type: Task
>            Reporter: Vladimir Steshin
>            Priority: Major
>
> For the join operations, we should have several SQL hints. One of them are forced join order hints. As an example, Oracle DB's analogue would be 'ORDERED', 'LEADING'. Might be combined with join operation type like merge, hash, nl like 'USE_NL', 'USE_MERGE'



--
This message was sent by Atlassian Jira
(v8.20.10#820010)