Vertica
Catalog Vertica schemas, tables, projections, views and columns from the V_CATALOG schema, with SQL lineage from query history.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | |
| Keys, constraints & indexes | Partial | |
| Procedures & functions | Partial | |
| Data lineage | Supported | |
| Lineage from query history | Supported | Statements collected from V_MONITOR.QUERY_REQUESTS. |
| Business glossary links | Supported | |
| Data quality probes | Supported | |
| Data profiling | Supported | |
| Data classification | Supported | |
| Chat with your data | Supported |
Connection settings
Create the connection on the Blindata Agent from Settings > Agents > Connections with the connection wizard, choosing Vertica in the technology step.
| Driver class | com.vertica.jdbc.Driver |
|---|---|
| JDBC URL | jdbc:vertica://localhost:5433/mydb |
| Authentication |
Service principal (shared technical user) User principal (personal credentials, BYOC) Ephemeral credentials (asked at each run)
|
| Crawling strategy | SQL |
The Blindata Agent does not include this driver: download the vendor JDBC driver and copy the .jar into the agent drivers folder, as described in
Add JDBC drivers.
Driver properties can be added under Advanced settings in the connection wizard.
Prerequisites & permissions
- A Blindata Agent installed with network access to Vertica.
- The vendor JDBC driver installed on the agent (see Add JDBC drivers).
USAGEon schemas and access toV_CATALOGsystem tables.SYSMONITORrole to readV_MONITORfor query history.
Set up metadata crawling
- Create the connection to Vertica on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents Vertica in the catalog and link it to the connection.
- In the CRAWLING tab add a crawling job with strategy SQL.
- Run a TEST to check the number of extracted objects, then RUN or schedule the job.
The job options and the column aliases of every extraction query are described in the Generic JDBC reference.
Lineage from query history
The agent can periodically extract executed statements from Vertica and send them to Blindata, where the SQL lineage engine turns them into dataflows. See the ready-made extraction query in Scheduling and statements extraction.