[
https://issues.apache.org/jira/browse/CALCITE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288906#comment-14288906
]
Julian Hyde commented on CALCITE-558:
-------------------------------------
I can see where you're coming from. Technically yes, it's an interpreter. But
it doesn't help solve the problem that you have to translate relational algebra
into a very different language (iterators and lots of lambdas) to get your
query to work.
We've had lots of people say 'yuck' when they find that they have to generate
java code in order to write a connector to a data source like mongo. I want to
make it easier for them.
By the way, another nice thing about a true relational interpreter is that you
could envisage building a debugger on top of it, so you could - say -
single-step the rows flowing through each operator.
> Add BINDABLE convention and make it the default convention for query root
> -------------------------------------------------------------------------
>
> Key: CALCITE-558
> URL: https://issues.apache.org/jira/browse/CALCITE-558
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> The default convention is currently ENUMERABLE, which means that to execute a
> query, and in particular to use the JDBC driver, RelNodes need to be able to
> convert themselves to code. This introduces a lot of dependencies that make
> CALCITE-466 difficult to solve.
> We propose to add a new convention that can be more easily implemented by a
> RelNode, using an interpreter or otherwise.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
