Transaction collisions when validating views on virtual tables in concurrent sessions
Details
| Detail name | Value |
|---|---|
| Changelog Number | 6991 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0, Exasol 6.1.0 |
| Fix Versions | Exasol 6.0.14, Exasol 6.1.1 |
| Resolution Date | 2018-11-23 |
Synpopsis
We have discovered two bugs in our system concerning view validation for views on virtual tables:
- If a transaction collision (and rollback) occurs during view validation, the exception text is wrongly stated as "Invalid view". Note that such conflicts are possible only when dealing with invalid views on virtual tables
- When invalid views on virtual tables are validated in concurrent sessions, only one session does the validation; the remaining sessions suffers transaction collisions and consequent rollbacks
Workaround
As a workaround, ensure views are not validated in concurrent sessions (autocommit should help). A view is validated upon creation and automatically at first (transactional) access after changes on underlying objects (in this case a virtual schema refresh).
