IMPORT FROM SCRIPT with table name instead of required column definition crashes

Details

Detail name Value
Changelog Number 7187
Type Bug
Status Resolved
Affected Versions EXASOL 6.0.0, Exasol 6.1.0, Exasol 6.2.0, Exasol 7.0.0
Fix Versions Exasol 8.0.0, Exasol 7.1.7
Resolution Date 2022-03-16

Background

Exasol 6.0 introduced the possibility to IMPORT FROM SCRIPT into a table or use it like a select to create a temporary result table.

Examples
-- into table
import into test.t from script etl.generate_seq WITH RECORDS='5';

-- into resultset / subselect
import into (val int) from script etl.generate_seq WITH RECORDS='5';

Problem

If you use parentheses around the table name, instead of providing column definitions, an internal server error occurs instead of a proper error message:

import into (test.t) from script etl.generate_seq WITH RECORDS='5';