[
https://issues.apache.org/jira/browse/CALCITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307950#comment-14307950
]
Julian Hyde commented on CALCITE-584:
-------------------------------------
There will be a mode where -- like today -- enumerable is the only active
convention, and we can quickly convert various kinds of tables to enumerable.
That should answer your concerns about search space.
Regarding UDFs that accept cursors. The user code will see a ResultSet. Now, as
to what is behind that ResultSet... it depends on which is the preferred engine
(interpreter vs enumerable).
If a user wants to write a "transform" that consumes relation(s) and produces
relation(s) they could take the simple route and write a function or the more
complex route and write a TableMacro. If the latter, their transform will be
able to be involved in the planning process involving rules, cost model and
more control over the format of the input and output data.
> Allow TableMacro to return Table other than TranslatableTable
> -------------------------------------------------------------
>
> Key: CALCITE-584
> URL: https://issues.apache.org/jira/browse/CALCITE-584
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
>
> The TableMacro.apply method used to return Table but in
> https://github.com/apache/incubator-calcite/commit/aa1f0983c126c23466deb990c96d6ff2dffd908c
> this changed to TranslatableTable. It seems reasonable to allow TableMacro
> to return other sub-types of Table, for example ScannableTable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
