[
https://issues.apache.org/jira/browse/CALCITE-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272596#comment-17272596
]
gaozhan ding commented on CALCITE-3753:
---------------------------------------
[~hyuan] hi, I noticed some messages in the commit.
{panel}
Also removed ambitious and impatient mode. User could override checkCancel and
throw VolcanoTimeoutException when appropriate (i.e. exceed 60 seconds, exceed
1000 ticks etc.) so that the VolcanoPlanner will stop exhaustive searching and
return the best plan so far.
{panel}
Could you provide some examples of the implementation of timeout mechanism you
mentioned?
> Remove rulematch ordering and execute substitution rule first
> -------------------------------------------------------------
>
> Key: CALCITE-3753
> URL: https://issues.apache.org/jira/browse/CALCITE-3753
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Haisheng Yuan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.23.0
>
> Attachments: image-2020-01-27-20-27-57-957.png
>
> Time Spent: 9h 40m
> Remaining Estimate: 0h
>
> In VolcanoPlanner, some rules e.g. ProjectMergeRule, PruneEmptyRule can be
> defined as SubstitutionRule, so that we can always try to match and execute
> them first (without deferring rule call). All the other rulematches doesn't
> need to be sorted and rules can be executed in any order they matched, since
> we are going to execute all of them anyway, sooner or later. Computing and
> comparing importances cause a lot of latency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
