[
https://issues.apache.org/jira/browse/CALCITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307990#comment-14307990
]
Julian Hyde commented on CALCITE-584:
-------------------------------------
The interpreter to handle ScannableTable, FilterableTable,
ProjectableFilterableTable would be fairly light weight. It would only have a
single node, and yes, just a few lines of code, most of the time. But it would
be able to add an extra node if the table rejects filters. Handling rejected
filters -- at run time -- is a really important requirement, and it is
something that EnumerableTableScan simply cannot do.
> 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)
