[
https://issues.apache.org/jira/browse/CALCITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307591#comment-14307591
]
Vladimir Sitnikov commented on CALCITE-584:
-------------------------------------------
I was not thinking you are proposing to get rid of QueryableTable (however it
could be a nice idea).
If we throw Scannable things all over the place, we would find ourselves stuck
with that codebase.
I want to merge Queryable vs Scannable somehow so:
1) Users could progressively enhance features without major rewrites from
Scannables to SuperScannables or whatever.
2) We could manage the complexity of multiple different **ables.
I hope there could be a way to make a blend of "Scannable and Queryable" so
newbies are not hurt.
{quote}At that point they will be happy to learn about rules and more advanced
SPIs.{quote}
Is that obvious, that "to get more features, you need to go from
ScannableTable" to "QueryableTable"?
Well, for a non-native speaker, the difference between "scannable" and
"queryable" is subtle.
> 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)
