Inserting into VARCHAR column may fail in commit check
Details
| Detail name | Value |
|---|---|
| Changelog Number | 7762 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 6.1.0 |
| Fix Versions | Exasol 6.1.3 |
| Resolution Date | 2019-05-13 |
Background
The complexity of DML operations is considerable. The data to be inserted or modified is received, transformed, distributed, partitioned and finally compressed.
To protect against data loss and data corruption, the written physical data is checked in commit for consistency and validity. If the check fails, the commit is aborted and hence the defective modification rolled back.
Problem
Exasol 6.1 introduced table partitioning (EXASOL-2265). For performance reasons, the complete data modification architecture was overhauled. These changes also affected distribution and column compression algorithms significantly.
With a very small probability an insert into a varchar column may fail in commit check. The problem is very data dependent (column values and ordering).
Workaround
There is no workaround or database parameter.
Repeating the critical statement has a chance to succeed though.
