Possible crash by failing import statements in virtual schema response
Details
| Detail name | Value |
|---|---|
| Changelog Number | 14220 |
| Type | Bug |
| Status | Open |
| Affected Versions | Exasol 7.1.0, Exasol 8.0.0 |
Background
A virtual schema is an abstraction layer which executes queries on a remote database and then sends the resultset back to the local database. Typically, these databases are not the same.
Queries on virtual schemas are broken down into two parts:
- A query (IMPORT) generated on the local Exasol database
- A read-only query executed on the remote database
Description
In sporadic cases, queries on virtual schemas which cause an exception return a general INTERNAL SERVER ERROR instead of the specific exception.
An internal server error is not able to be handled using pquery() in Lua scripts, which forces the entire script to fail.
Workaround
There is no workaround.
Fix
In case of an error, the correct database exception is signaled/propagated and can then be handled by a pquery() call in a LUA script.
