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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.21.0
• Fix Version/s: 1.22.0
• Component/s: core
• Labels: pull-request-available
• Assignee: Vladimir Sitnikov
• Reporter: Vladimir Sitnikov
• Created: 04/Jan/20 07:24
• Updated: 06/Mar/20 04:33
• Resolved: 09/Jan/20 09:07

Description

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.

Issue Links

• is related to: CALCITE-3673 ListTransientTable should not leave tables in the schema
• links to: GitHub Pull Request #1721