[
https://issues.apache.org/jira/browse/CALCITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307892#comment-14307892
]
Vladimir Sitnikov commented on CALCITE-584:
-------------------------------------------
{quote}BINDABLE vs ENUMERABLE conventions;{quote}
This is just an explosion of search space without much value.
I would rather have single convention, but allow helper method to convert
between row types.
For instance, we need to support UDF with {{cursor(...)}} parameters. Which
convention would that cursor implement?
Ok, that is not an easy question (especially when it comes to "ResultSet
convention"), but I see no much value out of BINDABLE.
Really.
> 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)
