Apache Kyuubi

Supported Data warehouses & lakehouses

Catalog Spark, Flink or Trino engines exposed through an Apache Kyuubi gateway.

Capabilities

CapabilitySupportNotes
Tables, views & columns Supported
Keys, constraints & indexes Not available
Procedures & functions Not available
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 JDBC (generic) in the technology step.

Driver classorg.apache.kyuubi.jdbc.KyuubiHiveDriver
JDBC URLjdbc:kyuubi://localhost:10009/default
Authentication
Service principal (shared technical user)
User principal (personal credentials, BYOC)
Ephemeral credentials (asked at each run)
Crawling strategyJDBC

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 Apache Kyuubi.
  • 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_SCHEMA or the vendor system views).
  • SELECT on the tables to analyze for data quality, profiling, classification and Chat with your data.

Set up metadata crawling

  1. Create the connection to Apache Kyuubi on the agent (see Connection settings) and use Test to verify it.
  2. Create or open the system that represents Apache Kyuubi in the catalog and link it to the connection.
  3. In the CRAWLING tab add a crawling job with strategy JDBC.
  4. 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.