CUBRID
Supported
Relational databases
Catalog CUBRID databases, tables, views and columns through the CUBRID JDBC driver.
Capabilities
| Capability | Support | Notes |
|---|---|---|
| Tables, views & columns | Supported | |
| Keys, constraints & indexes | Supported | |
| Procedures & functions | Partial | |
| Data lineage | Partial | |
| Lineage from query history | Not available | |
| 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 Cubrid in the technology step.
| Driver class | cubrid.jdbc.driver.CUBRIDDriver |
|---|---|
| JDBC URL | jdbc:cubrid:localhost:33000:demodb::: |
| Authentication |
Service principal (shared technical user) User principal (personal credentials, BYOC) Ephemeral credentials (asked at each run)
|
| Crawling strategy | JDBC |
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 CUBRID.
- The vendor JDBC driver installed on the agent (see Add JDBC drivers).
- A read-only user able to read the database catalog (JDBC metadata,
INFORMATION_SCHEMAor the vendor system views). SELECTon the tables to analyze for data quality, profiling, classification and Chat with your data.
Set up metadata crawling
- Create the connection to CUBRID on the agent (see Connection settings) and use Test to verify it.
- Create or open the system that represents CUBRID in the catalog and link it to the connection.
- In the CRAWLING tab add a crawling job with strategy JDBC.
- 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.