[CALCITE-418] Finish implementation of Interpreter

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Julian Hyde
• Created: 19/Sep/14 23:18
• Updated: 18/Dec/21 17:28

Description

In OPTIQ-416, we added the Interpreter class. It is able to handle RelNode types scan (over array-table at least), filter, project, values, sort; and RexNode types literal, inputRef, and calls to < and >.

This task is to complete implementation of the interpreter. This includes implementations of aggregate, join, union, minus, intersect, correlator RelNodes and of the set of built-in operators.

To prove that the interpreter is working, add a test that executes several complex queries over small data sets. (Maybe run the foodmart queries manually?) Also add a sub-class of SqlOperatorTest that interprets rather than generating code.

Issue Links

• is depended upon by: CALCITE-558 Add BINDABLE convention and make it the default convention for query root
• is depended upon by: CALCITE-107 Implement queries using an interpreter, as an alternative to code generation & compilation
• is related to: CALCITE-416 Execute logical RelNodes using an interpreter
• is related to: CALCITE-868 Add API to execute queries expressed as RelNode

Sub-Tasks

• Implement LEFT, RIGHT, FULL JOIN in interpreter: Open
• Implement windowed aggregate in interpreter: Open