Parallel IMPORT/EXPORT statements may not return the correct exception message
Details
| Detail name | Value |
|---|---|
| Changelog Number | 8176 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0, Exasol 6.2.beta1 |
| Fix Versions | Exasol 6.2.0, Exasol 6.1.5 |
| Resolution Date | 2019-06-21 |
Under rare circumstances, when an exception occurs during a parallel IMPORT or EXPORT (i.e. importing/exporting from/into multiple FILEs, STATEMENTs, TABLEs etc. in a single IMPORT/EXPORT statement), the original exception describing the error may not be returned to the user. In this case, another generic exception, which does not describe the actual problem, is returned instead (e.g. 'ETL-5400: Internal communication error occurred - please contact support').
For example, the following statement
IMPORT INTO (C1 INT) FROM JDBC AT EXA_CONN STATEMENT 'SELECT 1,2' STATEMENT 'SELECT 3,4';
may return the following exception
ETL-5400: Internal communication error occured - please contact support
instead of
ETL-5402: JDBC-Client-Error: Failed to initialize Query: ETL-6009: Number of columns in source (=2) and destination (=1) table differs
.
