You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/09 09:06:00 UTC
[jira] [Updated] (CALCITE-3677) Add assertion to
EnumerableTableScan constructor to validate if the table is suitable for
enumerable scan
[ https://issues.apache.org/jira/browse/CALCITE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated CALCITE-3677:
------------------------------------
Labels: pull-request-available (was: )
> Add assertion to EnumerableTableScan constructor to validate if the table is suitable for enumerable scan
> ---------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-3677
> URL: https://issues.apache.org/jira/browse/CALCITE-3677
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.21.0
> Reporter: Vladimir Sitnikov
> Assignee: Vladimir Sitnikov
> Priority: Major
> Labels: pull-request-available
>
> RelOptTableImpl#toRel (and some test methods) use EnumerableTableScan.create explicitly even in case the table is not implementable with enumerable scan.
> It does not hurt much for sql to rel translation, however, it is sad when a plan fails during execution.
> So EnumerableTableScan should have an assertion to prevent invalid uses.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)