[
https://issues.apache.org/jira/browse/CALCITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307962#comment-14307962
]
Vladimir Sitnikov commented on CALCITE-584:
-------------------------------------------
{quote} and we can quickly convert various kinds of tables to enumerable{quote}
Planner would have to consider crazy plans like
ENUMERABLE-BINDABLE-ENUMERABLE-BINDABLE.
Even if you invent some smart tricks to narrow down the search space, it would
have to check at least a single time both conventions for all the plan lines.
Then Bushy* comes in and we're out of time to plan a query.
> 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)
