[
https://issues.apache.org/jira/browse/CALCITE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307909#comment-14307909
]
Vladimir Sitnikov edited comment on CALCITE-584 at 2/5/15 8:47 PM:
-------------------------------------------------------------------
{quote}5. The test suite needs to continue to run. I do not want to refactor
the test suite (at least, not right now). Since the test suite is mostly in
core, the test suite will use the Interpreter by default{quote}
An interesting question is whether tests would got slower. Slowing down the
tests with no good reason is not the best idea.
was (Author: vladimirsitnikov):
{quote}5. The test suite needs to continue to run. I do not want to refactor
the test suite (at least, not right now). Since the test suite is mostly in
core, the test suite will use the Interpreter by default{quote}
An interesting question is whether tests would got slower.
> 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)
