[jira] [Resolved] (CALCITE-3677) Add assertion to EnumerableTableScan constructor to validate if the table is suitable for enumerable scan

["Vladimir Sitnikov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Sitnikov resolved CALCITE-3677.
----------------------------------------
    Fix Version/s: 1.22.0
       Resolution: Fixed

Fixed in https://github.com/apache/calcite/commit/2282b952e553a04c1f051e1bc42cd5910eb25f45

> 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
>             Fix For: 1.22.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)