Skip to main content
Collibra

Collibra

BETA
In this section, we provide guides and references to use the Collibra connector. Configure and schedule Collibra metadata workflows from the OpenMetadata UI:

​
How to Run the Connector Externally

To run the Ingestion via the UI you’ll need to use the OpenMetadata Ingestion Container, which comes shipped with custom Airflow plugins to handle the workflow deployment. If, instead, you want to manage your workflows externally on your preferred orchestrator, you can check the following docs to run the Ingestion Framework anywhere.

External Schedulers

Get more information about running the Ingestion Framework Externally

​
Requirements

To connect to Collibra, you will need:
  • Username: A user account with privileges to read all metadata in Collibra
  • Password: The password for the user account
  • Host and Port: The URL of your Collibra instance (e.g., https://your-instance.collibra.com)

​
Data Mapping and Assumptions

Following entities are supported and will be mapped to the OpenMetadata entities as shown below.
Collibra EntityOpenMetadata Entity
GlossaryGlossary
Glossary TermsGlossary Terms
DomainsDomains
CommunitiesDomains
  • Collibra glossaries will be mapped to OpenMetadata glossaries with their terms and relationships preserved.
  • When Enable Asset Enrichment is enabled, the connector will match Collibra assets to existing OpenMetadata entities and enrich them with descriptions, tags, and ownership information from Collibra without creating new assets.

​
Python Requirements

To run the Collibra ingestion, you will need to install: 
pip3 install "openmetadata-ingestion[collibra]"

​
Metadata Ingestion

All connectors are defined as JSON Schemas. Here you can find the structure to create a connection to Collibra. In order to create and run a Metadata Ingestion workflow, we will follow the steps to create a YAML configuration able to connect to the source, process the Entities if needed, and reach the OpenMetadata server. The workflow is modeled around the following JSON Schema

​
1. Define the YAML Config

​
2. Run with the CLI

First, we will need to save the YAML file. Afterward, and with all requirements installed, we can run: 
metadata ingest -c <path-to-yaml>
Note that from connector to connector, this recipe will always be the same. By updating the YAML configuration, you will be able to extract metadata from different sources.