You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/06/22 02:55:24 UTC

[jira] [Resolved] (OPTIQ-301) Add `Program` interface, a planner phase more general than current `RuleSet`

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

Julian Hyde resolved OPTIQ-301.
-------------------------------

    Resolution: Fixed

Fixed in master branch https://github.com/julianhyde/optiq/commit/3e4fb981d107af9bdd9b1b4090e5de45b8b0f1c5.

> Add `Program` interface, a planner phase more general than current `RuleSet`
> ----------------------------------------------------------------------------
>
>                 Key: OPTIQ-301
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-301
>             Project: optiq
>          Issue Type: Bug
>            Reporter: GitHub Import
>              Labels: github-import
>
> Currently `Framework.getPlanner` allows you to pass in an array of `RuleSet` objects. You can then invoke these one by one to get multi-phase optimization.
> A new `Program` interface generalizes `RuleSet`. It could, for instance, choose a different set of rules based on the input. It could invoke a particular planner engine (hep or volcano), and enable a particular set of traits. It could also invoke `RelNode` transformations that are ad hoc, not implemented in `RelOptRule`s.
> One of the current `Framework.getPlanner` methods is now deprecated and will be removed before optiq-0.9; new code should use a version that passes a list of `Program`.
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/julianhyde/optiq/issues/301
> Created by: [julianhyde|https://github.com/julianhyde]
> Labels: 
> Created at: Wed Jun 18 02:02:38 CEST 2014
> State: open



--
This message was sent by Atlassian JIRA
(v6.2#6252)