IMPORT FROM FBV with ERRORS INTO FILE produces an incorrect error message
Details
| Detail name | Value |
|---|---|
| Changelog Number | 5413 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | |
| Fix Versions | Exasol 6.1.0 |
| Resolution Date | 2018-02-05 |
The ERRORS INTO clause is not supported when IMPORTing from an FBV file. However, specifying ERRORS INTO FILE leads to a wrong error message.
For example, the following statement produces a wrong and/or confusing error message.
IMPORT INTO t1 FROM LOCAL FBV FILE 'test.fbv' (size=1 start=0, size=4 start=1) ERRORS INTO LOCAL CSV FILE 'test_errors.csv' REJECT LIMIT 10; [0A000] Feature not supported: IMPORT and EXPORT of local files is only supported via JDBC (except prepared statements) or EXAplus
However, when a table is specified for ERRORS INTO, the correct error message is displayed.
IMPORT INTO t1 FROM LOCAL FBV FILE 'test.fbv' (size=1 start=0, size=4 start=1) ERRORS INTO test_errors REJECT LIMIT 10; [42000] importing from FBV not allowed together with error table definition while executing 'IMPORT INTO t1 FROM FBV AT 'http://192.168.6.244:43347' FILE '4df804fe-0ef9-49d0-be64-372662ca4b06' (size=1 start=0, size=4 start=1) ERRORS INTO test_errors REJECT LIMIT 10 ;'
The error message displayed when a file is specified for ERRORS INTO should be similar to the case when a table is specified.