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

Posted to issues@calcite.apache.org by "Danny Chen (Jira)" <ji...@apache.org> on 2019/11/12 02:25:00 UTC

[jira] [Resolved] (CALCITE-482) Implement sql and planner hints

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

Danny Chen resolved CALCITE-482.
--------------------------------
    Fix Version/s: 1.22.0
       Resolution: Fixed

Fixed in [52bc246|https://github.com/apache/calcite/commit/52bc246d5e07510689635f407f4d9dc494b0af4d] !

> Implement sql and planner hints
> -------------------------------
>
>                 Key: CALCITE-482
>                 URL: https://issues.apache.org/jira/browse/CALCITE-482
>             Project: Calcite
>          Issue Type: Bug
>    Affects Versions: 1.0.0-incubating
>            Reporter: Vladimir Sitnikov
>            Assignee: Danny Chen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.22.0
>
>          Time Spent: 7.5h
>  Remaining Estimate: 0h
>
> Query optimizer can never be perfect, so it makes sense to implement hints to allow user better control the execution.
> For instance: "never merge this subquery with others" (`/+ no_merge/`), "treat those tables as leading ones" (`/*+ leading */`), etc.
> Hints would enable predictable performance and the planning time would be improved as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)