Vertica
On-premises, Vertica on AWS/Azure/GCP, Vertica Accelerator.
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 | Vertica cluster FQDN or IP (any node; the client driver discovers the cluster topology). |
| Port | Default 5433. |
| Database name | Vertica database name. |
| Schema(s) | Schemas to access. |
| Credentials | Username + password. LDAP or Kerberos if configured. |
| Access level | Read-only: USAGE on schemas, SELECT on tables/views/projections. |
Network considerations
On-premises (most common): VPN or dedicated circuit. Vertica clusters are typically internal.
Cloud deployments: Standard cloud networking (VPC peering, IP allowlisting).
All nodes must be reachable: Vertica driver connects to multiple nodes for load distribution. Firewall must allow access to all cluster nodes on port 5433.
Credential and auth management
Standard Vertica auth: Username + password.
LDAP: If Vertica authenticates against LDAP/AD.
Kerberos: Supported for enterprise SSO.
Resource pools: Flume should be assigned to a dedicated resource pool to isolate query workload. Confirm pool allocation.
Stored procedure and logic access
Vertica supports stored procedures and UDXs (User-Defined Extensions in C++, Java, Python, R). Standard SQL procedures: EXECUTE privilege required. UDXs: EXECUTE on the function. Introspection via V_CATALOG.USER_PROCEDURES and V_CATALOG.USER_FUNCTIONS.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Network reachability | telnet <host> 5433 | Connected |
| Authentication | SELECT 1; | Returns 1 |
| Identity | SELECT CURRENT_USER(); | Expected service account |
| Schema access | SELECT table_name FROM v_catalog.tables WHERE table_schema = '<schema>' | Lists tables |
| Permission audit | SELECT * FROM v_catalog.grants 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.