Sign inTry Free

Connect with Collibra Platform

On this page

Collibra is a data intelligence platform that helps organizations streamline data management, governance, and collaboration. It enables businesses to discover, understand, and trust their data by providing tools for data cataloging, data lineage, and policy management. Collibra enhances decision-making by ensuring data quality, security, and compliance across various data sources.

You can connect your SingleStore deployments to Collibra Platform using the SingleStore JDBC driver ("the driver"). The driver enables Catalog to register database information and extract the structure of the source into its schemas, tables, and columns. The driver can retrieve the following SingleStore database components:

  • Schemas

  • Tables

  • Views

  • Columns

  • Primary keys

Prerequisites

  • Access to an Edge site or a Collibra Cloud site.

  • Global System administration and Manage connections and capabilities permissions.

  • An active SingleStore deployment.

  • SingleStore JDBC driver version 1.2.6+ .jar file.

Configure the Connection to SingleStore

To connect using the SingleStore JDBC driver, perform the following tasks:

  1. Create a JDBC connection.

  2. Register a data source.

1. Create a JDBC Connection

Refer to Create a JDBC connection for information on creating a JDBC connection to SingleStore in Collibra Platform.

Specify the following connection settings while configuring the JDBC connection:

  • Name: Specify SingleStore.

  • Driver class name: Specify com.singlestore.jdbc.Driver.

  • Driver jar: Download the SingleStore JDBC driver .jar file from its GitHub repository, and upload the JAR file.

  • Connection String: Enter jdbc:singlestore://{host}:{port}/{db}, where:

    • host: IP address or the hostname of the SingleStore deployment.

    • port: Default is 3306.

    • db: Name of the SingleStore database to connect with.

Specify the following connection properties to configure the connection to your SingleStore deployment:

  • User: Username of the SingleStore database user with which to access the database.

  • Password: Password for the SingleStore database user.

Note

SingleStore does not support foreign keys. Hence, you must set the foreign-keys-strategy property to SKIP under Catalog JDBC Ingestion Edge capability.

2. Register a Data Source

Use the JDBC connection created earlier to register a data source. Refer to Register a data source via Edge for more information.

View Technical Lineage

You can also view the technical lineage graph for SingleStore to visualize the journey of the data objects in your data sources and data transformation details. Refer to Technical Lineage for more information.

Here are a few sample queries:

  • Visualize pipeline metadata for external functions:

    SELECT PIPELINE_NAME, CONFIG_JSON, STATE, CREATE_TIME
    FROM information_schema.PIPELINES
    WHERE DATABASE_NAME = '<database_name>';

  • Select and parse executed queries from history for internal relations:

    SELECT QUERY_TEXT FROM information_schema.MV_QUERIES
    WHERE ACTIVITY_NAME LIKE 'InsertSelect%';

References

Last modified: August 26, 2025

Was this article helpful?

On this page

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

  1. (Optional) Run the following command to view the associated signature files.

    curl undefined

  2. Download the signature file from the SingleStore release server.

    • Option 1: Click the Download Signature button next to the SingleStore file.

    • Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.

    • Option 3: Run the following command to download the signature file.

      curl -O undefined

  3. After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

    echo -n undefined |
        cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
          --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
          --bundle undefined \
          --new-bundle-format -
    Verified OK