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:13:00 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=16971987#comment-16971987 ] 

Danny Chen commented on CALCITE-482:
------------------------------------

Thanks everyone who has reviewed and given nice suggestions to the design doc, i'm planning merge this PR soon, if you have any other thoughts, we can discuss it in the following issues.

> 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
>          Time Spent: 7h 10m
>  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)