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

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/11/26 20:33:12 UTC

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

    [ https://issues.apache.org/jira/browse/CALCITE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226690#comment-14226690 ] 

Julian Hyde commented on CALCITE-482:
-------------------------------------

Can you sketch out what the API would look like?

> 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: Julian Hyde
>
> 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
(v6.3.4#6332)