aminghadersohi opened a new pull request, #44721: URL: https://github.com/apache/superset/pull/44721
### SUMMARY Classify Exasol syntax, missing-table, missing-column and insufficient-privilege diagnostics using the corresponding Superset error types, retaining the server's message (including position information). Ambiguous `object ... not found` messages remain generic rather than guessing table vs. column. The WebSocket driver's empty-error problem is already fixed by exasol/pyexasol#404 (PyExasol 2.4.1). This change supplies the missing engine-spec classifications, not an exception-chain workaround. ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF API-only: a missing-table diagnostic changes from `GENERIC_DB_ENGINE_ERROR` to `TABLE_DOES_NOT_EXIST_ERROR`; the server text is retained. No screenshots. ### TESTING INSTRUCTIONS - New focused engine-spec tests: unmodified spec **4 failed / 2 passed**; changed spec **6 passed** in the application dependency environment. - All changed-file pre-commit hooks pass, including mypy. - Equivalent engine-spec mappings plus a compatibility fix for the older pinned driver were verified through a disposable SQL Lab REST app on Exasol Nano 2026.2.0-nano.3: **14 passed / 0 failed**, both `exa://` and `exa+websocket://`, including a CREATE-SESSION-only account's permission failure. The old-driver control produced **10 failures / 4 healthy-query passes**. - To reproduce manually with PyExasol >=2.4.1, issue malformed SELECT, DROP TABLE for a nonexistent table, ALTER TABLE dropping a nonexistent column, and SELECT against a table the account cannot read. Verify both the returned error type and original diagnostic. A missing object SELECT remains generic with its full message. ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration - [ ] Introduces new feature or API - [ ] Removes existing feature or API -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
