Exasol
Exasol SaaS or self-managed.
Access mode: Read-only or read-write
Trino connector. Queryable via Flume’s Lakehouse. This system can be accessed both through its native protocol (for metadata introspection) and via Trino federation (for data profiling and cross-system analytical queries).
Required information
| Field | Details |
|---|---|
| Host / IP | Exasol cluster endpoint. SaaS: endpoint from Exasol console. |
| Port | Default 8563 (TLS) or 8562 (plain). |
| Schema(s) | Exasol schemas to access. |
| Credentials | Username + password. SaaS: user created in console. |
| Certificate fingerprint | Exasol uses certificate fingerprinting for TLS verification. Provide the server certificate fingerprint. |
| Access level | Read-only: SELECT on schemas/tables. Exasol uses a SQL-standard GRANT model. |
Network considerations
Exasol SaaS: HTTPS/TLS. VPC peering or IP allowlisting.
Self-managed: VPN or direct access. Default on port 8563 (TLS).
Exasol requires TLS for all connections. The certificate fingerprint must be provided or verified on first connection.
Trino access: Flume’s Lakehouse queries Exasol via the Trino Exasol connector over JDBC.
Credential and auth management
Standard Exasol auth: Username + password. Create a dedicated read-only user.
LDAP integration: Exasol supports external LDAP authentication.
Kerberos: Supported in enterprise deployments.
Connection limits: Exasol has per-user and global session limits. Confirm allocation for the Flume service account.
Priority groups: Assign the Flume user to a resource priority group to control query resource consumption.
Stored procedure and logic access
Exasol supports Lua and Java UDFs, plus scripting languages (Python, R, Java) via UDF scripts. EXECUTE privilege required. Introspection via SYS.EXA_ALL_SCRIPTS system table.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Network reachability | TLS connection to <host>:8563 | TLS handshake succeeds |
| Authentication | SELECT 1 | Returns 1 |
| Identity | SELECT CURRENT_USER | Returns service account |
| Schema access | SELECT * FROM SYS.EXA_ALL_TABLES WHERE TABLE_SCHEMA = '<schema>' | Lists tables |
| UDF listing | SELECT * FROM SYS.EXA_ALL_SCRIPTS WHERE SCRIPT_SCHEMA = '<schema>' | Lists scripts/UDFs |
| Permission audit | SELECT * FROM SYS.EXA_ALL_OBJECT_PRIVILEGES WHERE GRANTEE = '<user>' | Matches expected grants |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.