[
https://issues.apache.org/jira/browse/CALCITE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902723#comment-16902723
]
Danny Chan commented on CALCITE-482:
------------------------------------
Yeah, the 2 style hints are both very useful, for query hints, we can declare
some query config like time_zone, the resource; for table hints, we can declare
some dynamic properties that comes different every time this query is executed.
I agree to put selectivity into MEMO group, it is more like a metadata, while
the 2 kinds of hints i proposed in this patch is like a guideline or config
thing.
> 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 Chan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> 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
(v7.6.14#76016)
