[
https://issues.apache.org/jira/browse/CALCITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307487#comment-14307487
]
Julian Hyde commented on CALCITE-584:
-------------------------------------
If I haven't said this clearly enough: I am not proposing to get rid of
QueryableTable. Anyone who wants control over the row type should use
QueryableTable. Anyone who wants a cost model or custom rules should use
QueryableTable or TranslatableTable.
ScannableTable etc. are designed to be simple. I would welcome proposals for
how to make them simpler, but I don't want to hear how to make them faster,
because that is not a goal.
If we are successful, people will quickly write simple adapters using
ScannableTable, enjoy using Calcite, then come back and ask how they can make
their adapter smarter & faster. At that point they will be happy to learn about
rules and more advanced SPIs.
> 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)
