To collect metadata from a data source and add it into Collibra via Edge, Edge needs to be able to communicate with the data source. This is managed via an Edge connection. Once an Edge connection is established, the connection can be used by some of the Collibra capabilities to, for example, register the metadata or collect sample data.
You want to add the metadata of a Snowflake data source in Collibra and create technical lineage for it. By defining a JDBC connection between Edge and your Snowflake data source, you establish a secure line of communication between Collibra and your data source. This line of communication is then used to register the metadata and create technical lineage for it in your Collibra platform.
Multiple connection types are available. The connection type that you need to use depends on what you want to achieve. The following table contains the available Edge connection types and the associated capabilities.
| Connection type | Description |
|---|---|
| Azure |
Used for the integration Azure Data Lake Storage (ADLS) data sources. |
| AWS (Amazon Web Services) |
Used for the integration and protection of Amazon S3 data sources. |
| Databricks |
Used for the integration of Databricks Unity Catalog. |
| GCP (Google Cloud Platform) |
Used for the integration and protection of Google Cloud Storage and Dataplex data sources. |
|
Used to connect to Informatica Intelligent Cloud Services. |
|
|
Used to connect to JDBC data sources, for example, Snowflake, Salesforce, and PostgreSQL. Show associated capabilities
|
|
|
Used to connect to Matillion. |
|
| MicroStrategy |
Used to connect to MicroStrategy. |
| Power BI |
Used to connect to Power BI. |
| Shared Storage connection |
Used to access files from a shared folder. |
| Tableau |
Used to connect to Tableau Server or Tableau Online. |