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/09/20 01:37:33 UTC

[jira] [Resolved] (OPTIQ-416) Execute logical RelNodes using an interpreter

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

Julian Hyde resolved OPTIQ-416.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.1-incubating

Fixed in  http://git-wip-us.apache.org/repos/asf/incubator-optiq/commit/5fba93bf.

The current implementation works for a limited set of RelNode and RexNode types. I have logged OPTIQ-418 to complete the job. The Interpreter is nevertheless useful for testing purposes -- for example, to make sure that decorrelation has produced a viable plan -- as it stands.

> Execute logical RelNodes using an interpreter
> ---------------------------------------------
>
>                 Key: OPTIQ-416
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-416
>             Project: Optiq
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>             Fix For: 0.9.1-incubating
>
>
> Add an interpreter that can evaluate logical RelNodes (such as FilterRel, TableAccessRel).
> The motivation is similar to OPTIQ-107 but this feature request would interpret logical RelNodes, not RelNodes that implement EnumerableRel. This case would eliminate planning time as well as the janino step.
> We should explicit sources, sinks and start/run/stop methods. A bit less efficient, but gives us the opportunity for detailed tracing and even single-stepping.
> Put code in a new package net.hydromatic.optiq.impl.interpreter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)