Create a technical lineage via Edge

This topic provides an overview of the necessary steps to create a technical lineage via Edge.

You can also use the Collibra Catalog Cloud Ingestions API to create or update a technical lineage capability and start or schedule a synchronization to create a technical lineage. For more information about using APIs, go to Collibra Developer Portal.

To view the steps to create technical lineage for your data source, select the data source and connection type, if applicable. For a listed of supported data sources and their corresponding connection types, go to Supported data sources for technical lineage.

Tip 

Select a data source and the connection type if needed to see the related information. Currently, the information is shown for:

Amazon Redshift Azure Data Factory Azure SQL Data Warehouse Azure SQL Server Azure Synapse Analytics Databricks Unity Catalog (Beta) DB2 dbt Cloud dbt Core Google BigQuery Greenplum HiveQL IBM InfoSphere DataStage Informatica Intelligent Cloud Services Informatica PowerCenter Matillion MicroStrategy Oracle PostgreSQL Power BI MySQL Netezza SAP Hana Snowflake Spark SQL SQL Server SQL Server Integration Services Sybase Tableau Teradata Custom technical lineage

Which connection type do you use? JDBC connection Shared Storage connection For best technical lineage results, use the JDBC connection to ingest JDBC sources when possible, instead of using the Shared Storage connection with SQL files.

Choose another data source

X

My data source is not in this list.

• 
  Amazon Redshift
• 
  Azure Data Factory
• 
  Azure SQL Data Warehouse
• 
  Azure SQL Server
• 
  Azure Synapse Analytics
• 
  Custom technical lineage
• 
  Databricks Unity Catalog (Beta)
• 
  DataStage
• 
  DB2
• 
  dbt Cloud
• 
  dbt Core
• 
  Google BigQuery
• 
  Greenplum
• 
  Hive
• 
  Informatica Intelligent Cloud Services
• 
  Informatica PowerCenter
• 
  Matillion
• 
  MicroStrategy
• 
  MySQL
• 
  Netezza
• 
  Oracle
• 
  PostgreSQL
• 
  Power BI
• 
  SAP Hana
• 
  Snowflake
• 
  Spark SQL
• 
  SQL Server
• 
  SQL Server Integration Services
• 
  Sybase
• 
  Tableau
• 
  Teradata

Available vaults

Tip 

You can use a vault to add your data source information to your Edge site connection.	None AWS Secrets Manager Azure Key Vault CyberArk Vault Google Secret Manager HashiCorp Vault
	Select another vault I don't use a vault AWS Secrets Manager Azure Key Vault CyberArk Vault Google Secret Manager HashiCorp Vault

Before you begin

• Use Collibra Data Intelligence Platform 2024.02 or newer
• Use Collibra Data Intelligence Platform 2023.03 or newer.
• Use Collibra Data Intelligence Platform 2023.08 or newer
• Create an Edge site in Collibra Data Intelligence Platform. Ensure that you use Edge 2024.02 or newer.
• Install an Edge site.
• Enable technical lineage via Edge.

  To use technical lineage via Edge, you must enable the technical lineage for different data sources. You can also define some specific technical lineage settings on Edge. The technical lineage settings are general configurations that apply to all technical lineage features on Edge.

  Prerequisites and permissions

  The settings on the Services Configuration page are also available in the DGC service settings in Collibra Console.

  Note The Services Configuration page is not available by default. For more information, contact Collibra Support.

  Steps

  Depending on your environment, follow this procedure either on the Services Configuration tab of the Collibra settings or in Collibra Console:

  Collibra Console Collibra Settings

  Important Editing the Services Configuration from the Settings page isn't available in the latest UI (beta). If you use the latest UI, you can configure these settings only in Collibra Console. For more information, go to DGC service configuration settings.

  1. Open the Services Configuration page.

     1. On the main toolbar, click , and then click Settings.
        The Collibra settings page opens.
     2. Click Services Configuration.
     3. Click Edit configuration.

     Open the DGC service settings for editing:

     1. Open Collibra Console.
        Collibra Console opens with the Infrastructure page.
     2. In the tab pane, expand an environment to show its services.
     3. In the tab pane, click the Data Governance Center service of that environment.
     4. Click Configuration.
     5. Click Edit configuration.
  2. In the Lineage on Edge section, select the value of True for the technical lineage features that you want to enable.

     Setting	Description
     Databricks Unity Catalog synchronization via Edge	Enable the function of creating technical lineage for Databricks Unity Catalog. True Enable this feature. False Disable this feature.
     Power BI and Tableau synchronization enabled	Enable Data Catalog ingestion and technical lineage for Power BI and Tableau via Edge. True Enable this feature. False Disable this feature.
     Technical lineage via JDBC connection enabled	Enable the function of creating technical lineage for data sources that are connected by using JDBC connections on Edge. For a list of data sources that use the JDBC connection type, go to Supported data sources for technical lineage. True Enable this feature. False Disable this feature.
     Technical lineage for SQL via folder, ETL tools, and custom lineage on Edge enabled	Enable the function of creating technical lineage for data sources that are connected by using Shared Storage connections and APIs. With this function enabled, you can create custom technical lineage and technical lineage for ETL tools and JDBC data sources that are connected by using Shared Storage connections. For a list of data sources and connection types, go to Supported data sources for technical lineage. True Enable this feature. False Disable this feature.

  3. In the same Lineage on Edge section, enter the following information:

     Setting	Description
     DGC user name	The user name to be used to ingest metadata in Data Catalog via Collibra Data Lineage service.
     DGC user password	The password for the user to be used to ingest metadata.
     Collibra system name	Indicates whether you want to use the system or server name of a data source to match to the System asset that you create in Data Catalog. Only set the value to True when you have multiple databases with the same name. False The technical lineage via Edge ignores all system or server names that you specify for the Collibra system name settings when you add technical lineage capabilities. This is the default value. True The technical lineage via Edge uses the system or server names that you specify for the Collibra system name settings when you add technical lineage capabilities. Important If you use technical lineage via Edge and the lineage harvester to generate the technical lineage, the following values must be the same: The value for this setting. The value of the useCollibraSystemName property in the lineage harvester configuration file. If the values are different, the technical lineage synchronization ends with an error.

  4. Click Save all.
• Ensure that you meet the minimum network requirements.

  The lineage harvester uses the HTTPS protocol by default and uses port 443.

  Ensure that you satisfy your organization's firewall rules so that the Edge harvester can connect to all Collibra Data Lineage service instances in your geographic location:

  • 15.222.200.199 (techlin-aws-ca.collibra.com)
  • 18.198.89.106 (techlin-aws-eu.collibra.com)
  • 13.228.38.245 (techlin-aws-sg.collibra.com)
  • 54.242.194.190 (techlin-aws-us.collibra.com)
  • 35.197.182.41 (techlin-gcp-au.collibra.com)
  • 34.152.20.240 (techlin-gcp-ca.collibra.com)
  • 35.205.146.124 (techlin-gcp-eu.collibra.com)
  • 34.87.122.60 (techlin-gcp-sg.collibra.com)
  • 35.234.130.150 (techlin-gcp-uk.collibra.com)
  • 34.73.33.120 (techlin-gcp-us.collibra.com)

  The lineage harvester connects to different Collibra Data Lineage service instances based on your geographic location and cloud provider. If your location or cloud provider changes, the lineage harvester rescans all your data sources.

  • You have to allow all Collibra Data Lineage service instances in your geographic location.
  • Regardless of your geographic location, you have to allow one of the following. This is required to retrieve the API Key. No other data is transferred.
    • 54.242.194.190 (techlin-aws-us.collibra.com)
    • 18.198.89.106 (techlin-aws-eu.collibra.com)
    • 34.73.33.120 (techlin-gcp-us.collibra.com)
    • 15.222.200.199 (techlin-aws-ca.collibra.com)

  In addition, we highly recommend that you always allow the techlin-aws-us instance as a backup, in case the lineage harvester cannot connect to other Collibra Data Lineage service instances.

• Connect to a proxy server, if needed.

  CollibraData Lineage supports proxy server connection and authentication. Specifically, the technical lineage capability automatically applies all proxy settings that are configured on Edge. Technical lineage for Databricks Unity Catalog also supports a forward proxy that decrypts TLS traffic, a so-called man-in-the-middle (MITM) proxy.

  Warning If you intend to use a custom certificate to allow the Edge capability to connect to your data source, you must enable the --ca flag on Edge. However, the --ca flag only works in conjunction with the --proxy flag.

  If you enable the --proxy flag, you must use a proxy between the Edge capability and the Collibra Data Lineage service instance, or else ingestion will fail. This means that if you use a proxy or custom certificate between the Edge capability and your data source, you must also use a proxy between Edge and the Collibra Data Lineage service instance, or else ingestion will fail.

  Important You can use a man-in-the-middle (MITM) proxy between Edge and the Collibra Data Lineage service instances.

  View the results of the testing we did on different proxy combinations for JDBC data source integration

  Proxy between Edge and the data source	Proxy between Edge and the Collibra Data Lineage Service instance	Configuration	Connection to the service instance result	Connection to the data source result
  No proxy	No proxy	No proxy.properties No ca.pem	Supported	Supported
  No proxy	Proxy (not MITM)	No proxy.properties No ca.pem	Supported	Supported
  No proxy	MITM proxy	No proxy.properties No ca.pem	Supported	Supported
  Proxy (not MITM)	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param	Supported	Supported
  MITM proxy	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param ca.pem	Supported	Supported
  Proxy (not MITM)	Proxy (not MITM)	proxy.properties	Supported	Supported
  MITM proxy	MITM proxy	proxy.properties ca.pem	Supported	Supported

  Important You can use a man-in-the-middle (MITM) proxy between Edge and the Collibra Data Lineage service instances.

  View the results of testing we did on different proxy combinations for Azure Data Factory integration

  Proxy between Edge and Azure Data Factory	Proxy between Edge and the Collibra Data Lineage Service instance	Configuration	Connection to the service instance result	Connection to Azure Data Factory result
  No proxy	No proxy	No proxy.properties No ca.pem	Supported	Supported
  No proxy	Proxy (not MITM)	proxy.properties Added management.azure.com to noProxy param	Supported	Supported
  No proxy	MITM proxy	proxy.properties Added management.azure.com to noProxy param ca.pem	Not verified	Not supported
  Proxy (not MITM)	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param	Supported	Supported
  MITM proxy	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param ca.pem	Not supported	Fails to harvester metadata, but no error is raised. Empty SQLITE file is generated.
  Proxy (not MITM)	Proxy (not MITM)	proxy.properties	Supported	Supported
  MITM proxy	MITM proxy	proxy.properties ca.pem	Supported	Fails to harvester metadata, but no error is raised. Empty SQLITE file is generated.

  Important You can use a man-in-the-middle (MITM) proxy between Edge and the Collibra Data Lineage service instances.

  View the results of testing we did on different proxy combinations for MicroStrategy integration

  Proxy between Edge and MicroStrategy	Proxy between Edge and the Collibra Data Lineage Service instance	Configuration	Connection to the service instance result	Connection to MicroStrategy result
  No proxy	No proxy	No proxy.properties No ca.pem	Supported	Supported
  No proxy	Proxy (not MITM)	proxy.properties Added ec2-18-216-24-232.us-east-2.compute.amazonaws.com to noProxy param	Supported	Supported, but verified for HTTP source only, not HTTPS.
  No proxy	MITM proxy	proxy.properties Added ec2-18-216-24-232.us-east-2.compute.amazonaws.com to noProxy param ca.pem	Supported	Supported, but verified for HTTP source only, not HTTPS.
  Proxy (not MITM)	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param	Supported	Supported
  MITM proxy	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param ca.pem	Not supported	Supported, but verified for HTTP source only, not HTTPS.
  Proxy (not MITM)	Proxy (not MITM)	proxy.properties	Supported	Supported, but verified for HTTP source only, not HTTPS.
  MITM proxy	MITM proxy	proxy.properties ca.pem	Supported	Not verified

  Important You can use a man-in-the-middle (MITM) proxy between Edge and the Collibra Data Lineage service instances.

  View the results of testing we did on different proxy combinations for Power BI integration

  Proxy between Edge and Power BI	Proxy between Edge and the Collibra Data Lineage Service instance	Configuration	Connection to the service instance result	Connection to Power BI result
  No proxy	No proxy	No proxy.properties No ca.pem	Supported	Supported
  No proxy	Proxy (not MITM)	proxy.properties Added *.powerbi.com,login.microsoftonline.com to noProxy param	Supported	Supported
  No proxy	MITM proxy	proxy.properties Added *.powerbi.com,login.microsoftonline.com to noProxy param ca.pem	Supported	Supported
  Proxy (not MITM)	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param	Supported	Supported
  MITM proxy	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param ca.pem	Couldn't verify	Not supported
  Proxy (not MITM)	Proxy (not MITM)	proxy.properties	Supported	Supported
  MITM proxy	MITM proxy	proxy.properties ca.pem	Supported	Not supported, even with custom certificate in the connection.

  Important You can use a man-in-the-middle (MITM) proxy between Edge and the Collibra Data Lineage service instances.

  View the results of testing we did on different proxy combinations for Tableau integration

  Proxy between Edge and Tableau	Proxy between Edge and the Collibra Data Lineage Service instance	Configuration	Connection to the service instance result	Connection to Tableau result
  No proxy	No proxy	No proxy.properties No ca.pem	Supported	Supported
  No proxy	Proxy (not MITM)	proxy.properties Added prod-useast-b.online.tableau.com to noProxy param	Supported	Supported
  No proxy	MITM proxy	proxy.properties Added prod-useast-b.online.tableau.com to noProxy param ca.pem	Supported	Supported
  Proxy (not MITM)	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param	Supported	Supported
  MITM proxy	No proxy	proxy.properties Added techlin-gcp-dev.collibra.com to noProxy param ca.pem	Not supported	Supported
  Proxy (not MITM)	Proxy (not MITM)	proxy.properties	Supported	Supported
  MITM proxy	MITM proxy	proxy.properties ca.pem	Supported	Supported

  The following proxies are supported when you create technical lineage for Databricks Unity Catalog:

  • Path through (No authentication)
  • Path through (Basic authentication)
  • MITM (No authentication)
  • MITM (Basic authentication)
  • No proxy for noProxy hosts defined by Edge

  For Collibra Data Lineage to connect to a data source that requires a proxy, you can configure a forward proxy on Edge when you install your Edge site. For detailed steps, go to configure a forward proxy on Edge.

  When you add and synchronize the technical lineage capability on Edge, the technical lineage capability uses these proxy settings to establish connections to your data source to collect the metadata and create the technical lineage.

  Proxy server support is added to each technical lineage capability. If you encounter a connection error while synchronizing a technical lineage capability for a data source with a forward proxy configured, contact Collibra Support.
• Register the data source via Edge. Before you register the data source, ensure that you add the Catalog JDBC ingestion capability, so that CollibraData Lineage can stitch the data objects in your technical lineage to the assets in Data Catalog.
• Integrate Databricks Unity Catalog or register a Databricks file system.
• Register Azure Data Factory in the Azure Portal and assign the necessary permissions and access.

  Collibra Data Lineage uses Azure APIs to get the information necessary to build technical lineage from Azure Data Factory. Use this information to register Azure Data Factory in the Azure Portal and assign the necessary permissions and access.

  Warning Because the tasks covered in this topic are performed outside of Collibra, it is possible that the content changes without us knowing. We strongly recommend that you carefully read the source documentation.

  Topics in this section

  • Required values for your technical lineage for Azure Data Factory capability
  • Register your Azure Data Factory instance in the Azure Portal
  • Assign the API permissions
  • Create an authentication secret
  • Create an Azure Active Directory group and add your Azure Data Factory instance
  • Add your Azure Data Factory instance to a resource group
  • Retrieve the subscription ID of the resource group
  • Assign read-only permissions to the resource group

  Required values for your technical lineage for Azure Data Factory capability

  The tasks in this topic help you to identify the values you will need when you create an Azure connection and add a technical lineage for Azure Data Factory capability. You need the correct values for the fields shown in the following table.

  Important If you want to create a technical lineage for more than one Azure Data Factory instance, you need this information for each instance.

  Properties	Description
  Resource Group Name	The name of a resource group with the Reader role for the Azure Data Factory instance. To get the resource group name, go to Add your Azure Data Factory instance to a resource group.
  Service Principal ID	The Application account ID to connect to the Azure. For information on the Azure Service Principal user and the Application ID, go to the Azure documentation. To get the application ID for this field, go to Register your Azure Data Factory instance in the Azure Portal.
  Service Principal Secret	If you want to use the Service Principal authentication type, enter the application secret for the Service Principal. For information on the application secret value, go to the Azure documentation. If you want to use the Resource Owner Password Credentials authentication type, enter the password. Ensure that you select the corresponding authentication type when you add the Technical Lineage for ADF capability. To get the service principal secret, go to Create an authentication secret.
  Subscription ID	The subscription ID of the resource group. To get the subscription ID, go to Retrieve the subscription ID of the resource group.
  Tenant ID	The directory ID of your Azure Data Factory instance. For information on the Directory (tenant) ID, go to the Azure documentation. To get the directory ID, go to Register your Azure Data Factory instance in the Azure Portal.

  Register your Azure Data Factory instance in the Azure Portal

  Follow the Microsoft Azure instructions on how to register an application and refer to the following table for help with the various settings:

  Setting	Description
  Name	The name of your Azure Data Factory instance.
  Supported account types	The type of tenant. This indicates who can access the Azure Data Factory instance. Select Single tenant.
  Redirect URI	The location to which a user's client is redirected and where security tokens are sent after successful authorization. In this case, the redirect URI must be of the type Web. Leave this field empty. You don't have to specify a web location.

  The Azure Portal creates:

  • The Application ID. Use this ID as the value for the Service Principal ID field in the Azure connection.
  • The Directory ID. Use this ID as the value for the Tenant ID field in the technical lineage for ADF capability.

  Note When your Azure Data Factory instance is registered, you can find these two IDs in the Overview pane on the Azure Portal or in the upper-right menu.

  Assign the API permissions

  1. In the Azure Portal, click the Authentication pane, and then:
     1. Click the Advanced settings section.
     2. For the Allow public client flows option, click Yes.
  2. Click the API permissions pane, and then:
     1. For the permission type, click Delegated permissions.
     2. Assign the Azure Data Factory instance in Microsoft Azure the Microsoft Graph User.Read permission.

  The user now has the following permissions:

  • Microsoft Graph
  • User.Read

  Create an authentication secret

  1. In the sidebar navigation, in the Manage section, click Certificates and secrets.
  2. Ciick New client secret. Note that certificates are not supported.
     1. Enter a description.
     2. Use the date picker to specify an expiration date for the authentication secret.
     3. Click Add.
     An authentication secret is shown. Use this secret as the value for the Service Principal Secret field in the Azure connection.
     Important Make note of the authentication secret. For security purposes, It will not be available later. If you lose the authentication secret, you will need to create a new one.

  Create an Azure Active Directory group and add your Azure Data Factory instance

  1. Go to the Group Management page for your Azure Data Factory instance.
  2. Follow the Microsoft Azure instructions on how to Create and manage an Azure Active Directory (AD) Group, and refer to the following table for help with the various settings:

     Setting	Description
     Group Name	The name of the new Azure AD group that you are creating.
     Group Type	The type of the Azure AD group. Select Security.
     Service Principal	The identity an application uses to access Azure resources and APIs. Enter the Application ID that was generated when you registered Azure Data Factory in the Azure Portal.

  Add your Azure Data Factory instance to a resource group

  Your Azure Data Factory instance should already be part of a resource group. If it is, you can skip this step. If it's not, you need to create a resource group and add your Azure Data Factory instance to it.

  Use the group name as the value for the Resource Group Name field in the technical lineage for ADF capability.

  Tip The Data factories page shows all of your Azure Data Factory instances, including their subscriptions and resource groups. Check here to know if your instance is part of a resource group.
  

  Retrieve the subscription ID of the resource group

  On the Data factories page, click the resource group for the Azure Data Factory instance for which you want to create a technical lineage, and make note of the subscription ID.

  Use the subscription ID as the value for the Subscription ID field in the technical lineage for ADF capability.

  

  Assign read-only permissions to the resource group

  To gather the information needed for technical lineage, the resource group needs permission to read the APIs.

  1. Check to see which permissions the resource group has.

     1. On the Resource groups page, click Access control (IAM).
     2. In the Check access search box, type the name of the AD group.
        
     3. In the search results, click on the AD group to see the access assignments.
        

  If your resource group already has the Reader role, as shown in the previous image, this task is complete.

  2. If your resource group does not have the Reader role, click X in the upper-right corner, to close the Access assignments page.
     The Access control (IAM) page again appears.
     
  3. Click the Role assignments tab.
     
  4. Click Add > Add role assignment and follow the Microsoft Azure instructions on how to add a role assignment. Refer to the following table for help with the various settings:
     

     Setting	Description
     Roles	The role assignment for the resource group. Select Reader. The lineage harvester only needs read access.
     Members	Ensure that the User, group, or service principal radio button is selected. Search for and select the AD group.
     Conditions	No conditions are necessary. Click Next.
     Review + assign	Click Review +assign, to assign the Reader role to the resource group.

     After a few moments, the read-only permission is assigned to the resource group.

Requirements and permissions

The following requirements and permissions are needed for the technical lineage process. Additional, Edge-related roles and resources, are mentioned in each of the specific steps.

• A global role with the following global permissions:
  • Data Stewardship Manager
  • Manage all resources
  • System administration
  • Technical lineage
• A resource role with the following resource permissions on the community level in which you created the domain:
  • Asset: add
  • Attribute: add
  • Domain: add
  • Attachment: add
• As a technical lineage user, ensure that your Catalog Author global role has the following global permissions. With these permissions, Collibra Data Lineage can process the lineage and synchronize the results to Data Catalog to create technical lineage.
  • Catalog > Advanced Data Type > Add
  • Catalog > Advanced Data Type > Remove
  • Catalog > Advanced Data Type > Update
  • Catalog > Technical lineage
• As a Data Catalog user, ensure that your Edge integration engineer global role has the following global permissions. With these permissions, you can create connections and capabilities on Edge, configure the integration, and synchronize the integration.
  • Manage connections and capabilities
  • View Edge connections and capabilities
• As a Databricks Unity Catalog user, ensure that you have the following permissions in Databricks. The access token of this user must be specified in the Databricks connection so that Collibra Data Lineage can access the system tables (Public Preview) after connecting to Databricks Unity Catalog.
  • Enable the lineage system tables.
  • Have the USE CATALOG privilege to the system catalog.
    Example

    
  • USE_SCHEMA, and SELECT privileges to the system.access schema.
    Example

    
  For details, go to Enable system tables and Grant access to system tables in Databricks documentation.
  How to verify whether you have the right accesses in Databricks?

  1. Log into Databricks with the credentials that you use to create a Databricks connection on Edge.
  2. Run the following SQL query against your system.access catalog and schema in Unity Catalog:

     

     SELECT count(*) FROM column_lineage

  If you do not have the right accesses, the Could not get column lineage data error occurs when you synchronize the Technical Lineage for Databricks Unity Catalog capability. Contact Databricks support if you encounter issues on getting access to the system tables.

• Necessary permissions to all database objects that technical lineage via Edge accesses.
Tip Some data sources require specific permissions. For the data source selected above:
You need read access on the SYS schema.
You need read access on the SYS schema and the View Definition Permission in your SQL Server.
You need read access on information_schema:
• bigquery.datasets.get
• bigquery.tables.get
• bigquery.tables.list
• bigquery.jobs.create
• resourcemanager.projects.get
• bigquery.routines.get
• bigquery.routines.list
• bigquery.readsessions.create
• bigquery.readsessions.getData
• GRANT SELECT, at table level. Grant this to every table for which you want to create a technical lineage.
• The role of the user that you specify in the username property in lineage harvester configuration file must be the owner of the views in PostgreSQL.
The role of the user must be the owner of the views in PostgreSQL, and the username of the user must be specified in the JDBC connection that you use to access PostgreSQL.
You need read access on information_schema. Only views that you own are processed.
Ensure that your service account token has the Read-Only permission.
Ensure that you have the permission to copy the target/ directory, which is generated by running the dbt compile command, to a Shared Storage connection folder. For more information about the Shared Storage connection folder, go to Step 1 Create a Shared Storage connection.
• SELECT, at table level. Grant this to every table for which you want to create a technical lineage.
• Read access to the SYS schema or the tables in the schema.
You need Monitoring role permissions.
To create technical lineage from calculated views in an SAP HANA Classic on-premises data source, you also need the following permissions: 
• SELECT on the following views:
  • _SYS_REPO.ACTIVE_OBJECT
  • _SYS_REPO.ACTIVE_OBJECTCROSSREF
  • SYS.OBJECT_DEPENDENCIES
• The CATALOG READ system privilege
A role with the LOGIN option.
SELECT WITH GRANT OPTION, at Table level.
CONNECT ON DATABASE
The following permissions are required, regardless of the ingestion mode: SQL or SQL-API.
• Ensure that the Snowflake user has the appropriate allowed host list. For details, go to Allowing Hostnames in Snowflake documentation.
• You need a role that can access the Snowflake shared read-only database. To access the shared database, the account administrator must grant the IMPORTED PRIVILEGES privilege on the shared database to the user. The username of the user must be specified in the JDBC connection that you use to access Snowflake.
• If the default role in Snowflake does not have the IMPORTED PRIVILEGES privilege, you can click the Add property button to add a custom parameter with the following values specified:

  Field	Value
  Name	customConnectionProperties
  Type	Text
  Encryption	Select one of the following encryption methods:  Not encrypted (plain text) Encrypted with public key To be encrypted by Edge management server
  Role	metadata
You need read access on the DBC.
You need read access to the following dictionary views:
• all_tab_cols
• all_col_comments
• all_objects
• ALL_DB_LINKS
• all_mviews
• all_source
• all_synonyms
• all_views
You need read access on definition_schema.
• Your user role must have privileges to export assets.
• You must have read permission on all assets that you want to export.
• You have at least a Matillion Enterprise license.
• You have generated the Matillion certificate. Ensure that the certificate is signed by a certificate authority. Self-signed certificate is not supported when you create technical lineage via Edge.
• You have added the Matillion certificate to a Java truststore. For more information about adding a certificate to a Java truststore, go to Add a Certificate to a Truststore Using Keytool.
• You need the following Admin API permissions:
  1. The first call we make to MicroStrategy is to authenticate. We connect to:
     <MSTR URL>:<Port>/MicroStrategyLibrary/api-docs/ and use GET api/auth/login.
     For complete information, see the MicroStrategy documentation.
     If this API call can be made successfully, you can ingest the metadata.
  2. The same connection:
     <MSTR URL>:<Port>/MicroStrategyLibrary/api-docs/, but with GET api/model/tables/<tableId>.
     For complete information, see the MicroStrategy documentation.
     This endpoint is needed to create lineage and stitching.
     
• You need permissions to access the library server.
• The lineage harvester uses port 443. If the port is not open, you also need permissions to access the repository.
• You have to configure the MicroStrategy Modeling Service. For complete information, see the MicroStrategy documentation.
• Necessary permissions to all database objects that the lineage harvester accesses.
  
  Show me the data source-specific permissions

  Data source	Required permissions
  Amazon Redshift	You need read access on information_schema. Only views that you own are processed.
  Azure Data Factory	Ensure that you meet the Azure Data Factory-specific permissions described in Set up Azure Data Factory.
  Azure SQL server	You need read access on the SYS schema.
  Azure Synapse Analytics	SELECT, at table level. Grant this to every table for which you want to create a technical lineage. Read access to the SYS schema or the tables in the schema.
  Google BigQuery	If you are using the lineage harvester, you need read access on information_schema: bigquery.datasets.get bigquery.tables.get bigquery.tables.list bigquery.jobs.create bigquery.routines.get bigquery.routines.list If you are using Edge, you also need: resourcemanager.projects.get bigquery.readsessions.create bigquery.readsessions.getData
  Greenplum	A role with the LOGIN option.
  HiveQL	SELECT WITH GRANT OPTION, at Table level.
  IBM DB2	CONNECT ON DATABASE
  Informatica Intelligent Cloud Services	Your user role must have privileges to export assets. You must have read permission on all assets that you want to export.
  Matillion	You have at least a Matillion Enterprise license. You have generated the Matillion certificate. Ensure that the certificate is signed by a certificate authority. Self-signed certificate is not supported when you create technical lineage via Edge. You have added the Matillion certificate to a Java truststore. For more information about adding a certificate to a Java truststore, go to Add a Certificate to a Truststore Using Keytool.
  Microsoft SQL Server	You need read access on the SYS schema and the View Definition Permission in your SQL Server.
  MySQL	SELECT, at table level. Grant this to every table for which you want to create a technical lineage. Read access to the SYS schema or the tables in the schema.
  Netezza	You need read access on definition_schema.
  Oracle	You need read access to the following dictionary views: all_tab_cols all_col_comments all_objects ALL_DB_LINKS all_mviews all_source all_synonyms all_views
  PostgreSQL	GRANT SELECT, at table level. Grant this to every table for which you want to create a technical lineage. The role of the user that you specify in the username property in lineage harvester configuration file must be the owner of the views in PostgreSQL.
  Snowflake	The following permissions are required, regardless of the ingestion mode: SQL or SQL-API. You need a role that can access the Snowflake shared read-only database. To access the shared database, the account administrator must grant the IMPORTED PRIVILEGES privilege on the shared database to the user that runs the lineage harvester. If the default role in Snowflake does not have the IMPORTED PRIVILEGES privilege, you can use the customConnectionProperties property in the lineage harvester configuration file to assign the appropriate role to the user. For example: "customConnectionProperties": "role=METADATA"
  Teradata	You need read access on the DBC.
Important  Before you start the Power BI integration process, you have to perform a number of tasks in Power BI and Microsoft Azure. These tasks, which are performed outside of Collibra, are needed to enable the lineage harvester to reach your Power BI application and collect its metadata. For complete information, go to Set up Power BI.
Collibra Data Lineage supports:
• Power BI on the Microsoft Power Platform.
• Power BI on Fabric.
The configuration requirements and the integration are the same, regardless of your setup.
Important 
Before you start the Tableau integration process, you have to perform a number of tasks in Tableau. For complete information, go to the following topics:
• Set up Tableau
• Tableau roles and permissions

Steps

1. Set up Tableau.
2. Set up Power BI.
3. Set upMicroStrategy.
Create a JDBC connection.

For Collibra Data Lineage to connect to and retrieve metadata from your data source, create a JDBC connection.

If you have set up a JDBC connection when you registered the data source via Edge, you can use the existing JDBC connection.

For details about creating a JDBC connection, go to Create a JDBC connection.

5. Create an Azure Data Factory connection.

   For Collibra Data Lineage to connect to and retrieve metadata from Azure Data Factory, create an Azure connection.

   Before you begin

   Create an Edge site on K3S.

   Prerequisites

   • You have a global role that has the System administration global permission.
   • You have a global role that has the Manage Edge sites global permission.
   • You have a global role that has the Manage connections and capabilities global permission.

   Steps

   1. Open an Edge site.
      1. On the main toolbar, click , and then click Settings.
         The Collibra settings page opens.
      2. Click Edge.
         The Edge sites overview opens.
      3. Click the name of an Edge site in the Edge site overview.
         The Edge site page opens.
   2. Click Create Connection.
      The Connection settings page opens.
   3. In the Connections section, click Create Connection.
      The Create Connection dialog box appears.
   4. Select the Azure connection.
   5. Enter the connection information.

      Field	Description	Required
      Connection settings	This section contains the general settings of your connection.
      Name	The name of the Edge connection for Azure Data Factory.	Yes
      Description	The description of the connection.	No
      Connection provider	The connection provider, which determines the available connection parameters. Select the Azure connection.	Yes
      Connection parameters	This section contains the settings to connect to your data source.
      Service Principal ID	The Application account ID to connect to the Azure. For information on the Azure Service Principal user and the Application ID, go to the Azure documentation.	Yes
      Service Principal Secret	If you want to use the Service Principal authentication type, enter the application secret for the Service Principal. For information on the application secret value, go to the Azure documentation. If you want to use the Resource Owner Password Credentials authentication type, enter the password. Ensure that you select the corresponding authentication type when you add the Technical Lineage for ADF capability.	Yes
      Encryption options	Select the type of encryption used to store the Secret Access Key. The default is To be encrypted by Edge management server.	Yes
      Tenant ID	The directory ID of your Azure Data Factory instance. For information on the Directory (tenant) ID, go to the Azure documentation.	Yes

      Field	Description	Required
      Name	The name of the Edge connection for Azure Data Factory.	Yes
      Description	The description of the connection.	No
      Vault	The vault where you store your data source values.	No
      Service Principal ID	The Application account ID to connect to the Azure. For information on the Azure Service Principal user and the Application ID, go to the Azure documentation. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Service Principal Secret	If you want to use the Service Principal authentication type, enter the application secret for the Service Principal. For information on the application secret value, go to the Azure documentation. If you want to use the Resource Owner Password Credentials authentication type, enter the password. Ensure that you select the corresponding authentication type when you add the Technical Lineage for ADF capability. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Tenant ID	The directory ID of your Azure Data Factory instance. For information on the Directory (tenant) ID, go to the Azure documentation. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes

   6. Click Create.
6. Create a Databricks connection.

   If you integrated Databricks Unity Catalog, you had created a Databricks connection. You can use the Databricks connection when you add a technical lineage for Databricks Unity Catalog. If you registered your Databricks file system by using the JDBC connection instead, use this information to create a Databricks connection.

   Steps

   1. Open an Edge site.
      1. On the main toolbar, click , and then click Settings.
         The Collibra settings page opens.
      2. Click Edge.
         The Edge sites overview opens.
      3. Click the name of an Edge site in the Edge site overview.
         The Edge site page opens.
   2. Click Create Connection.
      The Connection settings page appears.
   3. In the Connections section, click Create Connection and select Databricks connection in the Create Connection dialog box.
      The Create Connection dialog box for Databricks connection opens.
   4. Enter the required information.

      Field	Description	Required
      Name	The name of the Edge connection for Databricks.	Yes
      Description	The description of the connection.	No
      Vault	The vault where you store your data source values.	No
      Workspace URL	Enter the URL of any Databricks workspace connected to Unity Catalog that you want to integrate. To retrieve the URL, log into Databricks and copy the URL. For example: https://123.cloud.databricks.com. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Access Token	The security token that was generated in Databricks for the workspace. The access token can be a personal access token or service principle token. We recommend using a service principle token. For information on the service principle token, go to the Databricks documentation. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes

      Field	Description	Required
      Connection settings	This section contains the general settings of your connection.
      Name	The name of the Edge connection for Databricks.	Yes
      Description	The description of the connection.	No
      Connection provider	The connection provider, which determines the available connection parameters. Select Databricks to connect to Databricks.	Yes
      Connection parameters	This section contains the settings to connect to your data source.
      Workspace URL	Enter the URL of any Databricks workspace connected to Unity Catalog that you want to integrate. To retrieve the URL, log into Databricks and copy the URL. For example: https://123.cloud.databricks.com.	Yes
      Access Token	The security token that was generated in Databricks for the workspace. The access token can be a personal access token or service principle token. We recommend using a service principle token. For information on the service principle token, go to the Databricks documentation.	Yes
      Encryption options	Select the type of encryption used to store the Secret Access Key. Default: To be encrypted by Edge management server.	Yes

   5. Click Create.
      The connection is added to the Edge site.
      
7. Create a dbt connection.

   For CollibraData Lineage to connect to and retrieve metadata from dbt Cloud, create a dbt connection.

   Before you begin

   Create an Edge site on K3S.

   Prerequisites

   • You have a global role that has the System administration global permission.
   • You have a global role that has the Manage Edge sites global permission.

   Steps

   1. Open an Edge site.
      1. On the main toolbar, click , and then click Settings.
         The Collibra settings page opens.
      2. Click Edge.
         The Edge sites overview opens.
      3. Click the name of an Edge site in the Edge site overview.
         The Edge site page opens.
   2. Click Create Connection.
      The Connection settings page appears.
   3. In the Connections section, click Create Connection.
      The Create Connection dialog box appears.
   4. Select dbt connection.
   5. Enter the connection information.

      Field	Description	Required
      Connection settings	This section contains the settings to connect to your data source.
      Name	The name of the connection.	Yes
      Description	The description of the connection. This field is also visible when you register content.	No
      Connection provider	The connection provider, which determines the available connection parameters. Select dbt connection.	Yes
      Connection parameters	This section contains general settings to connect to your data source.
      Admin URL	The dbt Cloud Administrative API that Collibra Data Lineage uses to download job artifacts. The default value is https://cloud.getdbt.com/api/v2. This field is used if you do not enter a value for the Environment Ids field in the Technical Lineage for dbt Cloud capability. If you enter values for both the Admin URL and Environment Ids fields, the Environment Ids field takes precedence.	No
      Metadata URL	The dbt Cloud Discovery API. The default value is https://metadata.cloud.getdbt.com/graphql. For details, go to Query the Discovery API in dbt documentation.	No
      Token Name	The name of the service token. It can be any unique meaningful name. How to get a service token and token value. Generate a Service token and ensure that you set the Read-Only permissions for CollibraData Lineage to work properly. Copy the token value when you save the service token. For details, go to Generating service account tokens in dbt documentation.	Yes
      Token Value	Enter the service token. Tip You can select To be encrypted by Edge management server or Encrypted with public key to indicate the encryption method.	Yes

      Field	Description	Required
      Name	The name of the connection.	Yes
      Description	The description of the connection. This field is also visible when you register content.	No
      Vault	The vault where you store your data source values.	No
      Admin URL	The dbt Cloud Administrative API that Collibra Data Lineage uses to download job artifacts. The default value is https://cloud.getdbt.com/api/v2. This field is used if you do not enter a value for the Environment Ids field in the Technical Lineage for dbt Cloud capability. If you enter values for both the Admin URL and Environment Ids fields, the Environment Ids field takes precedence. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	No
      Metadata URL	The dbt Cloud Discovery API. The default value is https://metadata.cloud.getdbt.com/graphql. For details, go to Query the Discovery API in dbt documentation. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	No
      Token Name	The name of the service token. It can be any unique meaningful name. How to get a service token and token value. Generate a Service token and ensure that you set the Read-Only permissions for CollibraData Lineage to work properly. Copy the token value when you save the service token. For details, go to Generating service account tokens in dbt documentation. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Token Value	Enter the service token. Tip You can select To be encrypted by Edge management server or Encrypted with public key to indicate the encryption method. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes

   6. Click Create.
8. Create an Informatica Intelligent Cloud Services connection.

   For CollibraData Lineage to connect to and retrieve metadata from Informatica Intelligent Cloud Services, create an Informatica Intelligent Cloud Services (IICS) connection.

   Before you begin

   • To create and use Informatica Intelligent Cloud Services (IICS) connection, use Collibra Data Intelligence Platform 2023.03 or later.
   • Create an Edge site on K3S.

   Prerequisites

   • You have a global role that has the System administration global permission.
   • You have a global role that has the Manage Edge sites global permission.
   • You have a global role that has the Manage connections and capabilities global permission.

   Steps

   1. Open an Edge site.
      1. On the main toolbar, click , and then click Settings.
         The Collibra settings page opens.
      2. Click Edge.
         The Edge sites overview opens.
      3. Click the name of an Edge site in the Edge site overview.
         The Edge site page opens.
   2. Click Create Connection.
      The Connection settings page appears.
   3. In the Connections section, click Create Connection.
      The Create Connection dialog box appears.
   4. Select Informatica Intelligent Cloud Services (IICS) connection.
   5. Enter the connection information.

      Field	Description	Required
      Connection settings	This section contains the settings to connect to your data source.
      Name	The name of the connection.	Yes
      Description	The description of the connection. This field is also visible when you register content.	No
      Connection provider	The connection provider, which determines the available connection parameters. Select Informatica Intelligent Cloud Services (IICS) connection.	Yes
      Connection parameters	This section contains general settings to connect to your data source.
      IICS URL	The URL of the Informatica Intelligent Cloud Services environment sign-in page. For example: https://dm-us.informaticaintelligentcloud.com.	Yes
      Username	The username that you use to sign in to Informatica Intelligent Cloud Services.	Yes
      Password	The password that you use to sign in to Informatica Intelligent Cloud Services. Tip You can select To be encrypted by Edge management server or Encrypted with public key to indicate the encryption method.	Yes

      Field	Description	Required
      Name	The name of the connection.	Yes
      Description	The description of the connection. This field is also visible when you register content.	No
      Vault	The vault where you store your data source values.	No
      IICS URL	The URL of the Informatica Intelligent Cloud Services environment sign-in page. For example: https://dm-us.informaticaintelligentcloud.com. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Username	The username that you use to sign in to Informatica Intelligent Cloud Services. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Password	The password that you use to sign in to Informatica Intelligent Cloud Services. Tip You can select To be encrypted by Edge management server or Encrypted with public key to indicate the encryption method. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes

   6. Click Create.
9. Create a Tableau connection.

   To retrieve data from Tableau, you have to connect to Tableau via the Edge site.

   Prerequisites

   • You have a global role that has the System administration global permission.
   • You have a global role that has the Manage Edge sites global permission.
   • You have a global role that has the Manage connections and capabilities global permission.
   • You have a resource role with the Configure external system resource permission, for example, Owner.
   • If you connect to Tableau Online, you have a Tableau user with at least Viewer rights.
   • If you connect to Tableau Server, you have a Tableau user with access to at least one site.
   • You have the necessary Tableau permissions.

   Steps

   1. Open an Edge site.
      1. On the main toolbar, click , and then click Settings.
         The Collibra settings page opens.
      2. Click Edge.
         The Edge sites overview opens.
      3. Click the name of an Edge site in the Edge site overview.
         The Edge site page opens.
   2. In the Connections section, click Create Connection.
      The Connection settings page appears.
   3. In the Connections section, click Create Connection.
      The Create Connection dialog box appears.
   4. Select Tableau connection.
   5. Enter the required information.
      

      Field	Description	Required
      Connection settings	This section contains general information about the connection.
      Name	The name of the connection. The name can be anything, as long as it is unique. Tip The name that you provide here is the name you have to select in the Tableau connection field, when adding the Technical Lineage for Tableau capability to the Edge site.	Yes
      Description	The description of the connection.	No
      Connection provider	The type of connection. Select Tableau connection.	Yes
      Connection parameters	This section contains connection authentication information.
      URL	The URL of your Tableau server.	Yes
      Authentication type	The authentication type for your connection to the Tableau server.	Yes
      Username/Token name	If you selected authentication type username, enter the username of the Tableau user. If you selected authentication type token, enter the personal access token name of the Tableau user.	Yes
      Password/Token secret	If you selected authentication type username, enter the password of the Tableau user. If you selected authentication type token, enter the personal access token secret of the Tableau user.	Yes
      Custom certificate	Optional field for uploading a custom server certificate, to connect to Tableau. Click Upload and search for your custom server certificate. You don't need to add the certificate to the Java Truststore. Edge stores the certificate as it does any other input parameter, and automatically uses it when connecting to Tableau.	No

      Field	Description	Required
      Name	The name of the connection. The name can be anything, as long as it is unique. Tip The name that you provide here is the name you have to select in the Tableau connection field, when adding the Technical Lineage for Tableau capability to the Edge site.	Yes
      Description	The description of the connection.	No
      Vault	The vault where you store your data source values.	No
      URL	The URL of your Tableau server. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Authentication Type	The authentication type for your connection to the Tableau server.	Yes
      Username/Token Name	If you selected authentication type username, enter the username of the Tableau user. If you selected authentication type token, enter the personal access token name of the Tableau user. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Password/Token Secret	If you selected authentication type username, enter the password of the Tableau user. If you selected authentication type token, enter the personal access token secret of the Tableau user. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
      Custom Certificate	Optional field for uploading a custom server certificate, to connect to Tableau. Click Upload and search for your custom server certificate. You don't need to add the certificate to the Java Truststore. Edge stores the certificate as it does any other input parameter, and automatically uses it when connecting to Tableau. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	No

   6. Click Create.
      

   What's next?

   Add the Technical Lineage for Tableau capability to the Edge site.

10. Create a Power BI connection.

    To retrieve data from Power BI, you have to connect to Power BI via the Edge site.

    Prerequisites

    • You have a global role that has the System administration global permission.
    • You have a global role that has the Manage Edge sites global permission.
    • You have a global role that has the Manage connections and capabilities global permission.
    • You have a resource role with the Configure external system resource permission, for example, Owner.
    • You have the necessary Power BI permissions.

    Steps

    1. Open an Edge site.
       1. On the main toolbar, click , and then click Settings.
          The Collibra settings page opens.
       2. Click Edge.
          The Edge sites overview opens.
       3. Click the name of an Edge site in the Edge site overview.
          The Edge site page opens.
    2. In the Connections section, click Create Connection.
       The Connection settings page appears.
    3. In the Connections section, click Create Connection.
       The Create Connection dialog box appears.
    4. Select Power BI connection.
    5. Enter the required information.
       

       Field	Description	Required
       Connection settings	This section contains general information about the connection.
       Name	The name of the connection. The name can be anything, as long as it is unique. Tip The name that you provide here is the name you have to select in the Power BI connection field, when adding the Technical Lineage for Power BI capability to the Edge site.	Yes
       Description	The description of the connection.	No
       Connection provider	The type of connection. Select Power BI connection.	Yes
       Connection parameters	This section contains connection authentication information.
       Tenant Domain	The domain associated with the Microsoft Azure tenant. This domain is either a default domain or a custom domain. For example, collibrapowerbi.onmicrosoft.com. Note Usually, you can find a list of Power BI tenant or server domains in your Azure Active Directory or in the top right menu.	Yes
       Authentication type	The authentication type for your connection to Power BI. Enter one of the following: Service Principal Resource Owner Password Credentials	Yes
       Application ID	The unique ID of the Microsoft Azure Application (client) ID.	Yes
       Username	The email address of your Azure Active Directory user. This field only applies if you entered Resource Owner Password Credentials in the Authentication type field.	No
       Password/Secret key	Your password (if you entered Resource Owner Password Credentials in the Authentication type field) or your secret key (if you entered Service Principal in the Authentication type field), for your Azure Active Directory user.	Yes
       Custom certificate	Optional field for uploading a custom server certificate, to connect to Power BI. Click Upload and search for your custom server certificate. You don't need to add the certificate to the Java Truststore. Edge stores the certificate as it does any other input parameter, and automatically uses it when connecting to Power BI.	No

       Field	Description	Required
       Name	The name of the connection. The name can be anything, as long as it is unique. Tip The name that you provide here is the name you have to select in the Power BI connection field, when adding the Technical Lineage for Power BI capability to the Edge site.	Yes
       Description	The description of the connection.	No
       Vault	The vault where you store your data source values.	No
       Tenant Domain	The domain associated with the Microsoft Azure tenant. This domain is either a default domain or a custom domain. For example, collibrapowerbi.onmicrosoft.com. Note Usually, you can find a list of Power BI tenant or server domains in your Azure Active Directory or in the top right menu. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
       Authentication type	The authentication type for your connection to Power BI. Enter one of the following: Service Principal Resource Owner Password Credentials	Yes
       Application ID	The unique ID of the Microsoft Azure Application (client) ID. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
       Username	The email address of your Azure Active Directory user. This field only applies if you entered Resource Owner Password Credentials in the Authentication type field. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	No
       Password/Secret key	Your password (if you entered Resource Owner Password Credentials in the Authentication type field) or your secret key (if you entered Service Principal in the Authentication type field), for your Azure Active Directory user. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
       Custom certificate	Optional field for uploading a custom server certificate, to connect to Power BI. Click Upload and search for your custom server certificate. You don't need to add the certificate to the Java Truststore. Edge stores the certificate as it does any other input parameter, and automatically uses it when connecting to Power BI. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	No

    6. Click Create.
       

    What's next?

    Add the Technical Lineage for Power BI capability to the Edge site.

11. Create a MicroStrategy connection.

    To retrieve data from MicroStrategy, you have to connect to MicroStrategy via the Edge site.

    Prerequisites

    • You have a global role that has the System administration global permission.
    • You have a global role that has the Manage Edge sites global permission.
    • You have a global role that has the Manage connections and capabilities global permission.
    • You have a resource role with the Configure external system resource permission, for example, Owner.
    • You have the necessary MicroStrategy permissions.

    Steps

    1. Open an Edge site.
       1. On the main toolbar, click , and then click Settings.
          The Collibra settings page opens.
       2. Click Edge.
          The Edge sites overview opens.
       3. Click the name of an Edge site in the Edge site overview.
          The Edge site page opens.
    2. In the Connections section, click Create Connection.
       The Connection settings page appears.
    3. In the Connections section, click Create Connection.
       The Create Connection dialog box appears.
    4. Select MicroStrategy connection.
    5. Enter the required information.
       

       Field	Description	Required
       Connection settings	This section contains general information about the connection.
       Name	The name of the connection. The name can be anything, as long as it is unique. Tip The name that you provide here is the name you have to select in the MicroStrategy connection field, when adding the Technical Lineage for MicroStrategy capability to the Edge site.	Yes
       Description	The description of the connection.	No
       Connection provider	The type of connection. Select MicroStrategy connection.	Yes
       Connection parameters	This section contains connection authentication information.
       URL	The URL of your MicroStrategy Intelligence Server.	Yes
       Authentication type	The authentication type for your connection to MicroStrategy.	Yes
       Username	The email address of your Azure Active Directory user. This field only applies if you entered Resource Owner Password Credentials in the Authentication type field.	No
       Password/Secret key	Your password (if you entered Resource Owner Password Credentials in the Authentication type field) or your secret key (if you entered Service Principal in the Authentication type field), for your Azure Active Directory user.	Yes

       Field	Description	Required
       Name	The name of the connection. The name can be anything, as long as it is unique. Tip The name that you provide here is the name you have to select in the MicroStrategy connection field, when adding the Technical Lineage for MicroStrategy capability to the Edge site.	Yes
       Description	The description of the connection.	No
       Vault	The vault where you store your data source values.	No
       MicroStrategy URL	The URL of your MicroStrategy Intelligence Server. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
       Username	The email address of your Azure Active Directory user. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
       Password	Your password for your Azure Active Directory user. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes

    6. Click Create.
       

    What's next?

    Add the Technical Lineage for MicroStrategy capability to the Edge site.

12. Create a Matillion connection.

    For Collibra Data Lineage to connect to and retrieve metadata from Matillion, create a Matillion connection.

    Before you begin

    • To create and use Matillion connection, use Collibra Data Intelligence Platform 2023.03 or later.
    • Create an Edge site on K3S.

    Prerequisites

    • You have a global role that has the System administration global permission.
    • You have a global role that has the Manage Edge sites global permission.
    • You have a global role that has the Manage connections and capabilities global permission.

    Steps

    1. Open an Edge site.
       1. On the main toolbar, click , and then click Settings.
          The Collibra settings page opens.
       2. Click Edge.
          The Edge sites overview opens.
       3. Click the name of an Edge site in the Edge site overview.
          The Edge site page opens.
    2. In the Connections section, click Create Connection.
       The Connection settings page appears.
    3. In the Connections section, click Create Connection.
       The Create Connection dialog box appears.
    4. Select Matillion connection.
    5. Enter the connection information.

       Field	Description	Required
       Connection settings	This section contains the settings to connect to your data source.
       Name	The name of the connection.	Yes
       Description	The description of the connection. This field is also visible when you register content.	No
       Connection provider	The connection provider, which determines the available connection parameters. Select Matillion connection.	Yes
       Connection parameters	This section contains general settings to connect to your data source.
       Matillion URL	The URL of your Matillion environment. For example, https://<domain name> or https://<IP address>.	Yes
       Authentication Type	The authentication details for signing in to Matillion. You can select one of the following values: Credentials Use the username and password authentication type. Token Use the token-based authentication type.	Yes
       Username	The username that you use to sign in to Matillion.	This field is required if you set the Authentication type field to Credentials.
       Password	The password that you use to sign in to Matillion. Tip You can select To be encrypted by Edge management server or Encrypted with public key to indicate the encryption method.	Yes

       Field	Description	Required
       Name	The name of the connection.	Yes
       Description	The description of the connection. This field is also visible when you register content.	No
       Vault	The vault where you store your data source values.	No
       Matillion URL	The URL of your Matillion environment. For example, https://<domain name> or https://<IP address>. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes
       Authentication Type	The authentication details for signing in to Matillion. You can select one of the following values: Credentials Use the username and password authentication type. Token Use the token-based authentication type.	Yes
       Username	The username that you use to sign in to Matillion. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	This field is required if you set the Authentication type field to Credentials.
       Password/Token secret	The password that you use to sign in to Matillion. Tip You can select To be encrypted by Edge management server or Encrypted with public key to indicate the encryption method. How to use your vault... To use your vault, do the following: In the Value Type field, select Vault Key. Enter the query value to identify the secret in your vault. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Engine Type Select one of the following: Key Value Database Engine Path The engine path to your vault where the value is stored. Secret Path The secret path to your vault where the value is stored. Field The name of the field to your vault where the value is stored. Note Only available if you selected Key Value in the Secret Engine Type field. Role The role specified in the Database engine. Note Only available if you selected Database in the Secret Engine Type field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Vault Name The name of your Azure Key Vault in your Azure Key Vault service where the value is stored. Secret Name The name of the secret in your vault where the value is stored. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the required information: Name Description Secret Name The name of the secret in your vault where the value is stored. Field If the secret stored in your AWS Secrets Manager is a JSON value, for example {"pass1": "my-password", "pass2": "my-password2"}, then you need to specify the Field to point to the exact JSON value that should be used. For example, Secret Name: edge-db-customer; Field: pass. Note If the secret stored in your AWS Secrets Manager is a plain string value, for example my-password, then you do not need to specify the Field. Example  To use your vault, do the following: In the Value Type field, select Vault Key. Enter the name of the secret in your vault where the value is stored. Example	Yes

    6. Click Create.
Create a Shared Storage connection.
A Shared Storage connection allows you to grant your capabilities access to files from a shared folder. This connection is especially useful for capabilities with large files, as you do not need to manually upload these files directly to Edge, but rather define the file path when creating the new connection.
Before you begin
• You have created an Edge site on K3S.
• You have installed an Edge site on K3S.
Note This connection type is not available for Edge sites created on EKS.
Prerequisites
• You have a global role that has the System administration global permission.
• You have a global role that has the Manage Edge sites global permission.
• You have a global role that has the Manage connections and capabilities global permission.
Steps
1. Create a folder on the server where your Edge site is installed, relative to --storage-path.
   When you create the Shared Storage connection, the location of this file appears next to the Folder field. For example, the location is indicated as Folder relative to /var/lib/edge/storage.
2. Open an Edge site.
   1. On the main toolbar, click , and then click Settings.
      The Collibra settings page opens.
   2. Click Edge.
      The Edge sites overview opens.
   3. Click the name of an Edge site in the Edge site overview.
      The Edge site page opens.
3. Click Create Connection.
   The Connection settings page appears.
4. In the Connections section, click Create Connection.
   The Create Connection dialog box opens.
5. Select Shared storage connection.
   The Create Connection dialog box for Shared storage connection opens.
6. Enter the connection information.

   Field	Description	Required
   Name	The name of the connection.	Yes
   Description	The description of the connection.	No
   Connection provider	Select Shared Storage Connection.	Yes
   Folder	Enter the name of your folder created in step 1. Subfolders are not allowed. Note Edge lists the location of this file to the right of this field.	Yes

   Field	Description	Required
   Name	The name of the connection.	Yes
   Description	The description of the connection.	No
   Folder	Enter the name of your folder created in step 1. Subfolders are not allowed. Note Edge lists the location of this file to the right of this field.	Yes

7. Click Create.
Create a Shared Storage connection.
A Shared Storage connection allows you to grant your capabilities access to files from a shared folder. This connection is especially useful for capabilities with large files, as you do not need to manually upload these files directly to Edge, but rather define the file path when creating the new connection.
Before you begin
• You have created an Edge site on K3S.
• You have installed an Edge site on K3S.
Note This connection type is not available for Edge sites created on EKS.
Prerequisites
• You have a global role that has the System administration global permission.
• You have a global role that has the Manage Edge sites global permission.
• You have a global role that has the Manage connections and capabilities global permission.
Steps
1. Create a folder on the server where your Edge site is installed, relative to --storage-path.
   When you create the Shared Storage connection, the location of this file appears next to the Folder field. For example, the location is indicated as Folder relative to /var/lib/edge/storage.
2. Open an Edge site.
   1. On the main toolbar, click , and then click Settings.
      The Collibra settings page opens.
   2. Click Edge.
      The Edge sites overview opens.
   3. Click the name of an Edge site in the Edge site overview.
      The Edge site page opens.
3. Click Create Connection.
   The Connection settings page appears.
4. In the Connections section, click Create Connection.
   The Create Connection dialog box opens.
5. Select Shared storage connection.
   The Create Connection dialog box for Shared storage connection opens.
6. Enter the connection information.

   Field	Description	Required
   Name	The name of the connection.	Yes
   Description	The description of the connection.	No
   Connection provider	Select Shared Storage Connection.	Yes
   Folder	Enter the name of your folder created in step 1. Subfolders are not allowed. Note Edge lists the location of this file to the right of this field.	Yes

   Field	Description	Required
   Name	The name of the connection.	Yes
   Description	The description of the connection.	No
   Folder	Enter the name of your folder created in step 1. Subfolders are not allowed. Note Edge lists the location of this file to the right of this field.	Yes

7. Click Create.
Prepare the SQL directory.

To create technical lineage for JDBC data sources by using the Shared Storage Connection, you must provide SQL files that include your SQL queries. Collibra Data Lineage processes the metadata based on your queries to create the technical lineage.

For more information about the connection types for different data sources, go to Supported data sources for technical lineage.

Steps

1. Create your SQL files. Ensure that the following requirements are met for the SQL files:

   • The SQL files must be UTF-8 encoded.
   • For better ingestion, include one SQL statement in one SQL file.
   • Collibra Data Lineage processes the SQL files in alphabetical order. The SQL files that include the Data Definition Language (DDL) statements must be processed before the SQL files that include the Data Manipulation Language (DML) statements. To ensure this order, name the SQL files such that those containing DDL statements come before those containing DML statements alphabetically.
   • The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. For more information, go to Add a technical lineage capability to your Edge site and Automatic stitching for technical lineage.

   For more information, go to Supported SQL syntax.

2. Store the SQL files in the folder that you created when you created the Shared Storage connection.

Example 1 SQL statements do not include schema and database names

This example shows the SQL files that include the queries on the Persons and JobInformation tables and the JobTitleView view. The SQL statements don't contain the database and schema values, so technical lineage via Edge uses the values of the Database and Schema fields in the technical lineage for SqlDirectory capability for stitching. The SQL files are named in a way that ensures the DDL statements are processed before the DML statement.

• The ddl-persons.sql file

  CREATE TABLE Persons (
      PersonID int,
      LastName varchar(255),
      FirstName varchar(255),
      Address varchar(255),
      City varchar(255)
  );	

• The ddl-jobinformation.sql file

  CREATE TABLE JobInformation (
      PersonID int,
      Department varchar(255),
      Title varchar(255)
  );

• The view-jobtitle.sql file

  CREATE VIEW JobTitleView AS
  SELECT
      Persons.PersonID,
      Persons.FirstName,
      Persons.LastName,
      JobInformation.Title
  from
      Persons
      INNER JOIN JobInformation ON Persons.PersonID = JobInformation.PersonId

Example 2 SQL statements include schema and database names

This example shows SQL files that include the queries on the Persons and JobInformation tables and the JobTitleView view. The SQL statements contain the database and schema names for each table and view, and Collibra Data Lineage uses them for stitching. The SQL files are named in a way that ensures the DDL statements are processed before the DML statement.

• The ddl-db1-schemaA-persons.sql file

  CREATE TABLE DB1.SchemaA.Persons (
      PersonID int,
      LastName varchar(255),
      FirstName varchar(255),
      Address varchar(255),
      City varchar(255)
  );

• The ddl-db2-schemaB-jobinformation.sql file

  CREATE TABLE DB2.SchemaB.JobInformation (
      PersonID int,
      Department varchar(255),
      Title varchar(255)
  );

• The view-db2-schemaC-jobtitleview.sql file

  CREATE VIEW DB2.SchemaC.JobTitleView AS
  SELECT
      Persons.PersonID,
      Persons.FirstName,
      Persons.LastName,
      JobInformation.Title
  from
     DB1.SchemaA.Persons
     INNER JOIN DB2.SchemaB.JobInformation ON Persons.PersonID = JobInformation.PersonId

16. Prepare the data source files.

    Prepare the data source files and store the data source files in the folder that you created when you created the Shared Storage connection in the previous step.

    Prerequisites

    You have IBM InfoSphere Information Server version 11.5 or newer.

    Steps

    1. Export the DataStage project files (DSX) for which you want to create a technical lineage. If you want to include runtime parameters in parameter set files in the technical lineage, ensure to export DataStage files with executables.
       

       Tip You can either export a DataStage project manually or automatically via command line.

    2. Store the DataStage files in your Shared Storage connection folder.

    3. Optionally, if your DataStage project uses environment variables, manually export the environment files (ENV).

    4. Give the environment files the same name as the DataStage project files. For example, if your project file is named datastage-project-1.dmx, name your environment file datastage-project-1.env.

    5. Store the environment files in the same Shared Storage connection folder.

       Important  

       • Collibra Data Lineage only supports DSX and ENV files.
       • You can have one DSX file per DataStage project.
       • You can have more than one DSX file in the Shared Storage connection folder.
       • You can have one or none ENV file per DSX file.
       • The name of the DSX file and the ENV file has to be the same.
17. Prepare the data source files.

    Prepare the data source files and store the data source files in the folder that you created when you created the Shared Storage connection in the previous step.

    Steps

    1. In the dbt Core environment, locate the target/ directory of your dbt project. The target/ directory must contain the manifest JSON file and compiled SQL files. This directory is created by running the dbt run and dbt compile commands.
    2. If the target/ directory does not exist or the directory does not contain the manifest JSON file or compiled SQL files, complete the following steps to create the directory and the required files:
       1. Set the profile of your dbt Core to the environment that you want to retrieve the lineage information from.
       2. Use the dbt compile command to generate SQL files. For details, go to About dbt compile command and Manifest JSON file in dbt documentation.

    3. Copy and paste the target/ directory in your Shared Storage connection folder and ensure that you maintain the folder structure. Your Shared Storage connection folder must contain all files and subdirectories, such as target/manifest.json and target/compiled/project-name/models/.

18. Prepare the data source files.

    Prepare the data source files and store the data source files in the folder that you created when you created the Shared Storage connection in the previous step.

    Prerequisites

    You have Informatica PowerCenter version 9.6 or newer.

    Steps

    1. Export the Informatica objects or repository for which you want to create a technical lineage to the Shared Storage connection folder. Make sure to export all objects, parameter files, mappings and sessions at the same time.
       Manually exporting Informatica objects in Informatica PowerCenter 10.0.0.

       1. Open Informatica PowerCenter Repository Manager.
       2. Connect to your Informatica repository.
       3. In the navigation panel, navigate to the workflow that contains the Informatica objects that you want to export.
       4. Right-click on the workflow and click Dependencies.
       5. In the Dependencies dialog box, do the following:
          1. Select Primary/Foreign Key dependencies.
          2. Select Global Shortcut dependencies.
          3. In the Object Types selector, select all object types except User-Defined.
       6. Click OK.
          The Dependencies dialog box closes.
          A dialog box with all Informatica objects appears.
       7. Select all objects.
       8. In the toolbar, click (Export to XML).
          
       9. Save the resulting XML files in your local folder.

       Exporting Informatica repository objects in Informatica PowerCenter via command line.

       1. In the Informatica PowerCenter Client or PowerCenter Services bin directories, open pmrep.
       2. Export Informatica PowerCenter repository objects.
          Note Make sure that you export the same Informatica PowerCenter repository objects as during a manual export.
       3. Save the resulting XML files in your local folder.

       Note 

       • If your folder contains previous versions of the parameter files, objects might be duplicated across different file versions. The duplicated objects cause CollibraData Lineage to ignore some transformations, resulting in missing lineage and error messages. For example, if a parameter file is exported after a column was added to a table, duplicated objects exist if the previous version of the parameter file remains in the folder. To avoid missing lineage, export all objects and parameter files at the same time.
       • All XML and parameter files, for example PAR, TXT or PRM files in this folder and its subfolders are taken into account when you create a technical lineage, but Collibra Data Lineage only shows a technical lineage for workflows that have mappings with sources, transformations and targets. Collibra supports the most common Informatica PowerCenter transformations. For more information, see the Informatica PowerCenter documentation.
       • When you export a workflow, ensure that all dependencies are included in the same export file. This applies whether you export the XML file manually or by using the command line. If any dependencies are missing for a workflow, the lineage information for the workflow will be missing in the technical lineage.
       • A technical lineage is created when the following tags are present in your XML file:
         • <REPOSITORY>
         • <FOLDER>
         • <SOURCE> / <TARGET>
         • <SESSION>
         • <MAPPING>
         • <TRANSFORMATION> (within a <MAPPING> tag)
       • If parameters are missing from the parameter files, the UNRESOLVED PARAMETERS analyze error will be displayed in the analysis results in the Sources tab page. For details, go to Analyze errors and possible solutions in Technical lineage Sources tab page.

    2. In the Shared Storage connection folder, create a folder named techlin-param and put the parameter files in the techlin-param folder.

19. Prepare the data source files.

    Prepare the data source files and store the data source files in the folder that you created when you created the Shared Storage connection in the previous step.

    Prerequisites

    • You have SQL Server Integration Services 2012 or newer with package format version 6 or newer.
    • You have Microsoft Visual Studio version 2012 or newer.

    Steps

    1. Export the SSIS files for which you want to create a technical lineage.

       Tip You can export them directly from the SQL Server Integration Services repository or via Microsoft Visual Studio. For more information, see the SQL Server Integration Services documentation.

    2. Store the SSIS files to the Shared Storage connection folder. Typically, the folder contains the following files:

       • SSIS package files (DTSX), containing the SQL Server Integration Services source code.
       • Connection manager files (CONMGR), containing environment and connection information.
       • Parameter files (PARAMS), if applicable.
       Note 

       • All files in this folder and subfolders are taken into account when you create a technical lineage. Technical lineage via Edge automatically detects data sources in the SSIS files.
       • Not all SSIS files are processed and shown in the technical lineage. Technical lineage via Edge retrieves all of the SSIS package files from the server, but only the files that contain lineage information, meaning those that contain a data flow, or Pipeline, are processed.
20. Which custom lineage definition option are you using?
    • Single-file definition

      You have to define the technical lineage in a single JSON file. Use the following format and code examples to create the JSON file, and then store the file in the folder that you created when you created the Shared Storage connection, earlier in this procedure.

      JSON file formatting for the single-file definition option

      If you opt for the single-file definition option, you use a lineage.json file to define the lineage between two or more data objects, and optionally include transformations details to create the custom technical lineage.

      The following sections in the JSON file define different parts in the resulting Collibra technical lineage graph:

      • tree, which defines the data object hierarchy. The data objects are shown as nodes in the technical lineage graph.
      • lineages, which defines the lineage relation. The lineage relations are shown as edges in the technical lineage graph. The edges represent the data flow from a source to a target.
      • codebase_files, which points to the source code files that include transformation details.

      To create a simple custom technical lineage, you need to include assets and lineages sections in your JSON file. You can add the transformation code in the lineages section.

      To create an advanced custom technical lineage, you need to include assets, lineages and codebase_files sections in your JSON file. You add references to the transformation code in source code files in the codebase_files section.

      Transformation code in both simple and advanced custom technical lineages is shown in the source code pane at the bottom part of the technical lineage graph.

      Requirements and restrictions

      The source code files must be in the same directory as the lineage.json file. Otherwise, an error occurs indicating that the lineage harvester cannot find the source code files.

      Sections

      Sections	Description
      version	The version of the JSON architecture. Specify the value of 1.0, which is the only supported version.
      tree	This section contains tree definitions of data objects between which lineages can be defined. The data objects are systems, databases, schemas, tables, views, columns, dashboards and reports. Each node of a tree contains the name, type and optionally children or leaves properties which form a hierarchy of data objects. You must define a node only once in this section. With the nested tree format, you can reuse the properties of one node for multiple children. For example, you can define a database once and use the children array to define multiple tables in the database. Tip Usually, the structure you map is the following: system > database > schema > table > column. The system is optional, unless the useCollibraSystemName property is set to true in your lineage harvester configuration file. Collibra Data Lineage can stitch these data objects to assets in Data Catalog. However, you can also map custom objects, for example dashboards and reports. Custom objects cannot be stitched to assets in Data Catalog. Important If the useCollibraSystemName property is set to false in your lineage harvester configuration file, do not specify the system data object in this section, or else stitching will fail.
      lineages	This section contains the path from a source to a target and defines the transformation code or transformation references to be processed by the Collibra Data Lineage service. Important If the useCollibraSystemName property is set to false in your lineage harvester configuration file, do not specify the system data object in this section, or else stitching will fail.
      codebase_files	This optional section defines the reference to source code files. Store the source code files that contain the transformation code in the same directory as the lineage.json file. Include this section only when you create an advanced custom technical lineage.

      tree section properties

      Properties	Description
      name	The name of your data object. Specify this property with the system name, database name, schema name, table name, view name or column name. The following rules apply when you specify this property: The names are case sensitive. The names of children and leaves can be identical if the children and leaves with the same names are in different parent nodes.
      type	The type of your data object. You can specify one of the following options: system, database, schema, table, view, column, dashboard or report. If the useCollibraSystemName property in your lineage harvester configuration file is set to true, the system data object is used to stitch to the System asset in Data Catalog. If the useCollibraSystemName property is set to false in your lineage harvester configuration file, do not specify the system data object in this section, or else stitching will fail.
      children	The sub-objects that have a hierarchical relation to the defined data object. Each child can contain children properties, except for the penultimate child. The penultimate children property must contain the leaves property. The leaves property cannot contain a children property. For example, you can use the children property to define a table and use the leaves properties to define columns that have a relation to the table node. Each child and leave have the name and type properties and the optional catalog_fullname, catalog_domain_id, catalog_asset_type_name and catalog_asset_type_uuid properties.
      leaves	The sub-objects of an object that is defined in a children property, but cannot have sub-objects of their own. A technical lineage is defined as relations between leaf nodes of the tree. The value of the type property of the leaves property must be column or report. Indirect and table-level technical lineages are not supported. For the workarounds to create a table level or indirect technical lineage, see Programming considerations.

      lineage section properties

      Properties	Required	Description
      src_path	Yes	The hierarchical path to the source data object. This data object is defined as a leaf in the tree section. This property represents where the data comes from for a transformation.
      trg_path	Yes	The hierarchical path to the target data object. This data object is defined as a leaf in the tree section. This property represents where the data flows to.
      <data objects>	Yes	An ordered array of data object names. This array is required to define the sub-objects of the src_path and trg_path properties. Specify the array with the data object names that start from the top of the tree section and finish at a leaf node. This example shows data objects that can be stitched: system > database > schema > table > column. This example shows data objects that cannot be stitched: dashboard > report > column. If the useCollibraSystemName property in your lineage harvester configuration file is set to true, the system data object is used to stitch to the System asset in Data Catalog. If the useCollibraSystemName property is set to false in your lineage harvester configuration file, do not specify the system data object in this section, or else stitching will fail.
      mapping	Yes Simple custom technical lineage only	The mapping name. This property specifies a name for the transformation code.
      source_code	Yes Simple custom technical lineage only	The transformation code, which determines how the technical lineage is constructed. The transformation code can be a descriptive string or a SQL statement that manipulates data.
      mapping_ref	No Advanced custom technical lineage only	This property contains the name of the mapping reference to the transformation code in source code files. This property also contains the position and length of the transformation code to be highlighted in the technical lineage graph.
      source_code	No Advanced custom technical lineage only	The name of the source code file that contains the transformation code. The transformation code can be a SQL statement, code that manipulates data or a descriptive string. The source code file must be in the same folder as the lineage.json file.
      mapping	No Advanced custom technical lineage only	The unique descriptor of a part of transformation code in a source code file that is in the same directory as the lineage.json file. A source code file can contain different parts of transformation code that represent different data flows. This property indicates the referenced data flow. The value of this property is the same as the value of the mapping_refs property in the codebase_files section.
      codebase_pos	No Advanced custom technical lineage only	The positions indicate a string of the transformation code in a source code file to be highlighted in the bottom part of the Collibra technical lineage graph. The whole lines that include the transformation code are highlighted. The string must be a subset of the string of the transformation code that is defined by the pos_start and pos_len properties of the mapping_refs property in the codebase_files section.
      pos_start	No Advanced custom technical lineage only	The start position of the string of the transformation code to be highlighted. The start position is in characters, not bytes. The value must be equal to or greater than the value of the pos_start property of the mapping_refs property in the codebase_files section.
      pos_len	No Advanced custom technical lineage only	The length of the string of the transformation code to be highlighted. The length is in characters, not bytes. Specify a value in the following range: Equal to or greater than 1. Less than or equal to the length of the string that is defined by the pos_len property of the mapping_refs property in the the codebase_files section. For example, if you specify "pos_start": 10 and "pos_len": 160 in the codebase_files section, specify a value for this property in the range of 0 - 149.

      codebase_files section properties

      Properties	Description
      <source code path>	The file path to source code files that contain the transformation code. The transformation code can be a SQL statement or code that manipulates data. The source code file must be in the same directory as the lineage.json file.
      mapping_refs	The mapping of the transformation code and the position of the transformation code that is shown in the bottom part of the technical lineage graph. This property defines a string of the transformation code in the source code file to be shown in the technical lineage graph. The string must include the string that is defined by the pos_start and pos_len properties of the mapping property in the lineage section.
      <mapping>	The unique descriptor of a part of transformation code in a source code file that is in the same directory as the lineage.json file. A source code file can contain different parts of transformation code that represent different data flows. This property indicates the referenced data flow. The value must match the value of the mapping property in the lineage section.
      pos_start	The start position of the string of the transformation code. The start position is in characters, not bytes. Specify a value in the following range: Equal to or greater than 0. Less than or equal to the value of the pos_start property in the mapping property in the lineage section.
      pos_len	The length of the string of the transformation code. The length is in characters, not bytes. Specify a value in the following range: Greater than or equal to 1. Less than or equal to the length of the source code file minus the start position. For example, if you specify "pos_start": 10 and the file length is 160 characters, specify a value for this property in the range of 1 - 150.

      Programming considerations

      Currently, there is no native support for indirect and table-level lineages. As a workaround, you can specify "type": "column" and "name": "*" for the leaves property to create a table level or indirect technical lineage. With this specification, the indirect technical lineage is shown as a solid line instead of a dashed line in the Collibra technical lineage graph, and is always shown, regardless of whether or not the Show indirect dependencies option is enable or disabled.

      Example

      For some example JSON files, go to Custom technical lineage JSON file examples.

      Single file-definition JSON file examples

      This section shows some example lineage.json files for simple custom technical lineage and advanced custom technical lineage.

      Each example can be used to generate technical lineage graphs in Collibra to represent the IOT_JSON and IOT_DEVICES_PER_COUNTRY tables with the following columns:

      IOT_JSON	IOT_DEVICES_PER_COUNTRY
      CCA3	COUNTRY
      DEVICE_ID	NUMBER_DEVICES

      Example JSON file for a simple custom technical lineage

      In the following example, the tree section defines the IOT_JSON and IOT_DEVICES_PER_COUNTRY tables and columns. The tables are in a schema named COLLIBRA. The COLLIBRA schema is in a database named COLLIBRA and a system named Databricks.

      Important If you define the System asset in your lineage.json file, the useCollibraSystemName property in your lineage harvester configuration file must be set to true; otherwise, relations will not be created between the relevant assets in Collibra and stitching will fail.

      To show the transformation code at the bottom of the technical lineage graph, specify the mapping and source_code properties in the lineages section.

      { 
        "version": "1.0",
        "tree": [
      	{ 
      	    "name": "Databricks", 
                 "type": "system",
      	    "children": [
      	       { 
      		   "name": "COLLIBRA", 
      		   "type": "database",
      		   "children": [
             	      { 
      	                  "name": "COLLIBRA", 
      	                  "type": "schema",
      	                  "children": [
      		             { 
      		                 "name": "IOT_JSON", 
      		                 "type": "table",
      		                 "leaves": [
      		                    { 
      			                "name": "CCA3", 
      			                "type": "column"
      			            },
      			            { 
      			                "name": "DEVICE_ID", 
      			                "type": "column"
      			            }
      			         ]
      		             },
      		             { 
      		                 "name": "IOT_DEVICES_PER_COUNTRY",
      			         "type": "table",
      			         "leaves": [
      			            { 
      			                 "name": "COUNTRY", 
      			                 "type": "column"
      			            },
      			            { 
      			                "name": "NUMBER_DEVICES",  
      			                "type": "column"
      			            }
      			        ] 
      	                    }
      		        ]
      		    }
      	          ]
      	       }
                 ]
             } 
        ],
        "lineages": [
      	 {
               "src_path": [
      	     {
      	         "system": "Databricks"
      	     },
      	     {
      	         "database": "COLLIBRA"
                  },
      	     {
      	         "schema": "COLLIBRA"
      	     },
      	     {
      	         "table": "IOT_JSON"
      	     },
      	     {
      	         "column": "CCA3"
      	     }
      	  ],
      	  "trg_path": [
      	     {
      	         "system": "Databricks"
      	     },
      	     {
      	         "database": "COLLIBRA"
      	     },
      	     {
      	         "schema": "COLLIBRA"
      	     },
      	     {
      	         "table": "IOT_DEVICES_PER_COUNTRY"
      	     },
      	     {
      	         "column": "COUNTRY"
      	     }
      	  ],
      	  "mapping": "dev_no_bat_per_country_view",
      	  "source_code": "INSERT INTO ... SELECT CCA3 AS COUNTRY...FROM IOT_JSON"
       	 }
        ]
      }

      Example JSON file for an advanced custom technical lineage

      In the following example, the tree section defines the IOT_JSON and IOT_DEVICES_PER_COUNTRY tables and columns. The tables are in a schema named COLLIBRA. The COLLIBRA schema is in a database named COLLIBRA and a system named Databricks.If you define the System asset in your lineage.json file, the useCollibraSystemName property in your lineage harvester configuration file must be set to true; otherwise, relations will not be created between the relevant assets in Collibra and stitching will fail.

      {
        "version": "1.0",
        "tree": [
           { 
               "name": "Databricks", 
      	  "type": "system",
      	  "children": [
      	     { 
      	         "name": "COLLIBRA", 
      	         "type": "database",
      	         "children": [
                         { 
      	                "name": "COLLIBRA", 
      	                "type": "schema",
      	                "children": [
      	                   {
      		               "name": "IOT_JSON",
      		               "type": "table",
      		               "leaves": [
      		                  { 
      		                      "name": "CCA3", 
      			              "type": "column"
      			          },
      			          { 
      			              "name": "DEVICE_ID", 
      			              "type": "column"
      			          }
      			       ] 
      			   },
      			   { 
      			       "name": "IOT_DEVICES_PER_COUNTRY", 
      			       "type": "table",
      			       "leaves": [
      			          { 
      			              "name": "COUNTRY",
      			              "type": "column"
      			          },
      			          { 
      			              "name": "NUMBER_DEVICES", 
      			              "type": "column"
      			          }
      		              ] 
                               }
                           ]
                        }
                     ] 
                  }
               ] 
            }
        ],
        "lineages": [
           {
               "src_path": [
      	     {
                      "system": "Databricks"
                  },
      	     {
      	         "database": "COLLIBRA"
      	     },
      	     {
      	         "schema": "COLLIBRA"
      	     },
      	     {
      	         "table": "IOT_JSON"
      	     },
      	     {
      	         "column": "CCA3"
      	     }
      	  ],
      	  "trg_path": [
      	     {
      	         "system": "Databricks"
      	     },
      	     {
      	         "database": "COLLIBRA"
      	     },
      	     {
      	         "schema": "COLLIBRA"
      	     },
      	     {
      	         "table": "IOT_DEVICES_PER_COUNTRY"
      	     },
      	     {
      	         "column": "COUNTRY"
      	     }
      	 ],
      	 "mapping_ref": 
      	    {
      	        "source_code": "transforms.sql",
      	        "mapping": "dev_no_bat_per_country_view",
      	        "codebase_pos": [
      	           { 
      	              "pos_start": 71, "pos_len": 69
      	           } 
                     ]
                 } 
            }
        ],
        "codebase_files": 
          {
             "transforms.sql": 
      	   {
      	       "mapping_refs": 
      	          {
      	              "dev_no_bat_per_country_view": 
      	          {
      	              "pos_start": 0,
      	              "pos_len": 246
      	          }
      	       }
      	   }
          }
        }

      Example technical lineage graphs

      Both example lineage.json files generate the following technical lineage graph, which contains 2 nodes and 1 edge.

      

      The following technical lineage graph is generated by using the example lineage.json file for an advanced custom technical lineage. The bottom part shows the transformation code that generated the data flow.

      In the lineages section, the pos_start property is specified with 71 and the pos_len property is specified with 69. The specifications indicate that the transformation code that starts at position 71 and the following 69 characters are highlighted in blue. Line 2 in the technical lineage graph contains the highlighted transformation code.

      

    • Batch definition

      You can define the custom technical lineage in any number of JSON files. Use the following format and code examples to create the JSON files, and then store the files in the folder that you created when you created the Shared Storage connection, earlier in this procedure.

      JSON file formatting for the batch-definition option

      If you opt for the batch definition option, you need to create a folder with all of your JSON files and specify the folder in your lineage harvester configuration file. The harvester then accesses the folder, zips the content and ingests it for processing.

      Which files do you need in your batch folder?

      Let's say that you create a folder and name it custom-lineage. In this folder, you need the following:

      • Exactly one metadata file, to provide the JSON architecture version, the data source type, and asset type UUIDs of the assets you want to include in the technical lineage.
      • Optionally, one or more asset files, to provide a list of data objects you want to include in the technical lineage and define the data object hierarchy to achieve stitching.
      • One or more lineage files, to define the lineage relation between two or more data objects.
      • Optionally, a subfolder of source code files that contain the transformation code.
        

      Example 

      __CUSTOM-LINEAGE__
          ├── assets-domain1.json
          ├── assets1.json
          ├── lineage.json
          ├── lineage-extra.json
          ├── metadata.json
          └── source_codes
              ├── sc1.sql
              └── sc2.py

      Metadata file

      Your metadata file has to be named metadata.json. Format the file as shown in the following image:

      Example 

      {
        "version": 3, 
        "application_name": "databricks",
        "asset_types":{
          "Column":{"uuid": "00000000-0000-0000-0000-000000031008"},
          "Table":{"uuid": "00000000-0000-0000-0000-000000031007"},
          "Database":{"uuid": "00000000-0000-0000-0000-000000031006"},
          "Schema":{"uuid": "00000000-0000-0000-0001-000400000002"}
        }
      }

      Tip 

      View the JSON schema for the metadata file

      {
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "type": "object",
        "properties": {
          "version": {
            "anyOf": [
              {
                "type": "integer"
              },
              {
                "type": "string",
                "pattern": "^\\d+$"
              }
            ]
          },
          "application_name": {
            "type": "string"
          },
          "asset_types": {
            "type": "object",
            "additionalProperties": {
              "type": "object",
              "properties": {
                "uuid": {
                  "type": "string"
                }
              }
            }
          }
        },
        "required": [
          "application_name",
          "version"
        ]
      }
      

      Section	Description
      version	The version of the JSON architecture. For batch-file instruction, the value must be 3.
      application_name	The type of data source for which you are creating a technical lineage. This helps us to better understand your needs and make more informed decisions concerning future integrations.
      asset_types	The asset types and UUIDs of the asset types you want to include in the technical lineage. Important If you choose to include asset files in your batch definition, the values (meaning the asset types) that you specify in this property must match the values that you specify in the type properties in your asset files. Likewise, the values that you specify in this property must match the asset types that you mention in your lineage files.

      Assets files

      Optionally, you can include one or more assets files. You use asset files to provide the list of data objects you want to include in the technical lineage and define the data object hierarchy. The props property allows you to specify the full names and domain IDs of the assets.

      Tip 

      Don't use asset files in the following scenarios:

      • Your data source consists of the traditional (System) > Database > Schema > Table > Column asset types and hierarchy. In that case, full names are automatically, correctly constructed.
      • You are working with assets that are not part of that traditional asset hierarchy (in which case, you need to use the props property to achieve stitching) and you define props in one or more lineage files.

      The names of your assets files have to follow the format assets<something-unique>.json.

      Asset files can consist of nodes, parent, and leaf kinds of assets. In the following example code, we used the nodes property to specify the highest levels of the data object hierarchy that we want to view in the technical lineage: Database and Schema. We then used the parent and leaf properties to build out the lower levels of the data object hierarchy: Table and Column, respectively.

      parent assets represent what we traditionally refer to as the table-level lineage. leaf assets represents what we traditionally refer to as the column-level lineage.

      Keep in mind that the property names nodes, parent, and leaf are designed to be non-restrictive, so you can define a hierarchy to reflect the hierarchy of any asset types (similar to the database > schema > table > column hierarchy), including your custom asset types.

      Tip For examples of how to configure the props property, as shown in the following code examples, see Using the props property.

      Tip 

      View the JSON schema for assets files

      {
          "$schema": "https://json-schema.org/draft/2020-12/schema",
          "$defs": {
              "assetData": {
                  "type": "object",
                  "properties": {
                      "name": {
                          "type": "string"
                      },
                      "type": {
                          "type": "string"
                      }
                  },
                  "required": [
                      "name",
                      "type"
                  ]
              },
              "props": {
                  "type": ["object", "null"],
                  "properties": {
                      "fullname": {
                          "type": "string"
                      },
                      "domain_id": {
                          "type": "string"
                      }
                  },
                  "required": [
                      "fullname"
                  ]
              }
          },
          "anyOf": [
              {
                  "type": "object",
                  "properties": {
                      "nodes": {
                          "type": "array",
                          "items": {
                              "$ref": "#/$defs/assetData"
                          }
                      },
                      "props": {
                          "$ref": "#/$defs/props"
                      },
                      "parent": {
                          "$ref": "#/$defs/assetData"
                      },
                      "leaf": {
                          "$ref": "#/$defs/assetData"
                      }
                  },
                  "required": [
                      "nodes",
                      "parent",
                      "leaf"
                  ]
              },
              {
                  "type": "object",
                  "properties": {
                      "nodes": {
                          "type": "array",
                          "items": {
                              "$ref": "#/$defs/assetData"
                          }
                      },
                      "props": {
                          "$ref": "#/$defs/props"
                      },
                      "parent": {
                          "$ref": "#/$defs/assetData"
                      }
                  },
                  "required": [
                      "nodes",
                      "parent"
                  ]
              },
              {
                  "type": "object",
                  "properties": {
                      "nodes": {
                          "type": "array",
                          "items": {
                              "$ref": "#/$defs/assetData"
                          }
                      },
                      "props": {
                          "$ref": "#/$defs/props"
                      }
                  },
                  "required": [
                      "nodes"
                  ]
              }
          ]
      }

      Property	Description
      nodes	A JSON element in which you specify the highest levels of the hierarchy. In the example code, the nodes specify the hierarchy of GCS File System > GCS Bucket. Example  { "nodes": [ { "name": "GCS1", "type": "GCS File System" }, { "name": "GCS-B1", "type": "GCS Bucket" } ], "props": { "fullname": "<full name of the GCS Bucket asset>", "domain_id": "<domain of the GCS Bucket asset>" } }
      name	The name of the node data object. The value is case-sensitive. Case-sensitivity exception The value of the name property is not case-sensitive for Database, Schema, Table and Column assets. For those assets, any capitalization discrepancies are rectified during processing, and the names always appear in uppercase in the technical lineage. However, assets files are not needed or recommended for these asset types.
      type	The type of data object of the specified node, for example: System, Database, Dashboard, or Report. The value is case-sensitive. Important The values (meaning the asset types) that you specify for this property must match the values that you specify in the asset_types property in your metadata file.
      parent	A lower-level data object in a hierarchy for which the highest levels are specified in the nodes section. The parent property represents what we traditionally refer to as the table-level lineage. When specifying parent data objects, you also have to include the nodes information, as shown in the following example code. Example  { "nodes": [ { "name": "GCS1", "type": "GCS File System" }, { "name": "GCS-B1", "type": "GCS Bucket" } ], "parent": { "name": "DIR1", "type": "Directory" }, "props": { "fullname": "<full name of the Directory asset>", "domain_id": "<domain of the Directory asset>" } } Tip Each parent object can contain leaf data objects. For example, you can use the parent property to specify a table, and use the leaf properties to specify the columns in the table.
      name	The name of the parent data object. The value is case-sensitive. Case-sensitivity exception The value of the name property is not case-sensitive for Database, Schema, Table and Column assets. For those assets, any capitalization discrepancies are rectified during processing, and the names always appear in uppercase in the technical lineage. However, assets files are not needed or recommended for these asset types.
      type	The asset type of the parent data object, for example: Table, Directory, Dashboard, or Report. The value is case-sensitive. Important The values (meaning the asset types) that you specify for this property must match the values that you specify in the asset_types property in your metadata file.
      leaf	The lowest level data object in your hierarchy. The leaf property represents what we traditionally refer to as the column-level lineage. When specifying leaf data objects, you also have to include the nodes and parent information, as shown in the following example code. The names of parents and leaf data objects can be identical if the data objects with the same names are sub-objects of different nodes data objects. Example  { "nodes": [ { "name": "GCS1", "type": "GCS File System" }, { "name": "GCS-B1", "type": "GCS Bucket" } ], "parent": { "name": "DIR1", "type": "Directory" }, "leaf": { "name": "data.xls", "type": "File" }, "props": { "fullname": "<full name of the File asset>", "domain_id": "<domain of the File asset>" } }
      name	The name of the leaf data object. The value is case-sensitive. Case-sensitivity exception The value of the name property is not case-sensitive for Database, Schema, Table and Column assets. For those assets, any capitalization discrepancies are rectified during processing, and the names always appear in uppercase in the technical lineage. However, assets files are not needed or recommended for these asset types.
      type	The asset type of the leaf data object, for example: Column, Dashboard, or Report. The value is case-sensitive. Important The values (meaning the asset types) that you specify for this property must match the values that you specify in the asset_types property in your metadata file.
      props	This property allows you to specify the full name and domain ID of an asset for the purpose of stitching, regardless of asset type hierarchy. When you add the props property to define the full name of an asset, it applies to the last asset in the array. Tip For examples of how to configure the props property and how to use it for a custom hierarchy, see Using the props property. Important considerations You don't need to use this property for the traditional (System) > Database > Schema > Table > Column asset types and hierarchy. In fact, assets files are not needed or recommended for those asset types, as the full name is automatically, correctly constructed for that hierarchy. Instead, use this property to specify the full names of assets that are not part of that traditional asset hierarchy. You must specify in your metadata file the asset types and UUIDs of all the assets types used. If the useCollibraSystemName property in your lineage harvester configuration file is set to true, the system data object is used to stitch to the System asset in Data Catalog. If the useCollibraSystemName property is set to false in your lineage harvester configuration file, do not specify the system data object in this section, or else stitching will fail. A word about file processing order and inadvertently specifying the same asset more than once Assets files and lineage files are processed in the following order: first, all assets files in alphabetical order, followed by all lineage files in alphabetical order. If you choose to specify props for an asset, we recommend that you do so in either an assets file or a lineage file; not both. For any asset that is inadvertently defined more than once, the first occurrence, with respect to the processing order, is the occurrence that is used. In other words: If you inadvertently define a single asset, with props, in both an assets file and a lineage file, the props values in the assets file are used. If you inadvertently define a single asset, with props, more than once in a single assets file, or in multiple assets files, the first occurrence of the asset, with respect to the processing order, is used along with the props values defined for that occurrence of the asset.
      fullname	The full name of the asset in Collibra. Names are case-sensitive.
      domainId	The reference ID of the domain in which the asset exists in Collibra.

      Using the props property

      The following examples offer some guidance as to when to use the props property and how to configure it.

      Show me a typical scenario using the props property for a custom hierarchy

      First off, let's examine why you don't need to use the props property for the traditional database > schema > table > column hierarchy. Let's say you have an assets file in which you define a leaf kind of asset:

      {
        "nodes": [{
          "name": "Snowflake",
          "type": "System"
        }, {
          "name": "DB1",
          "type": "Database"
        }, {
          "name": "PUBLIC",
          "type": "Schema"
        }],
        "parent": {
          "name": "T1",
          "type": "Table"
        },
        "leaf": {
          "name": "COL1",
          "type": "Column"
        }
      }
      

      In this case, the full name of the leaf asset (in this case a Column asset) is automatically and correctly constructed as: "snowflake>DB1>PUBLIC>T1>COL1". In fact, for the traditional database type of hierarchy, you don't even need to use asset files, much less the props property.

      However, for the following custom hierarchy, you can use the props property to specify the correct full name of the leaf asset, in this case a File asset.

      {
      "nodes": [{
        "name": "gcs",
        "type": "GCS File System"
      }, {
        "name": "bucket1",
        "type": "GCS Bucket"
      }, {
        "name": "/",
        "type": "Directory"
      }],
      "parent": {
        "name": "examples",
        "type": "Directory"
      },
      "leaf": {
        "name": "data.xls",
        "type": "File"
      },
      "props": {
        "fullname": "gcs > bucket1/examples/data.xls",
        "domain_id": "<domain in which the file asset resides>"
      }
      

      If you don't provide the full name of the leaf asset, it will be constructed using the default traditional formatting (system) > database > schema > table > column. The result would be the full name: "gcs > bucket1 > / > examples > data.xls". However, this is not the correct construction for File assets. The full name provided in the example above ensures the correct construction, so that stitching is achieved.

      Show me example configurations for the props property

      • A props property in a nodes section describes the last asset in the array. In this example, you are specifying the full name and domain ID of the Schema asset "SCH1", not the Database asset "DB1".
        

        {
        	"nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}],
        	"props": {
        		"fullname": "<full name of the Schema asset>",
        		"domain_id": "<domain of the Schema asset>"
        		}
        }
        

      • If you also want to specify the full name and domain ID of the Database asset, you need two entries, as follows:
        

        {
        	"nodes": [{"name":"DB1", "type": "Database"}],
        	"props": {
        		"fullname": "<full name of the Database asset>",
        		"domain_id": "<domain of the Database asset>"
        	        }
        }

        }	
               "nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}],
        	"props": {
        		"fullname": "<full name of the Schema asset>",
        		"domain_id": "<domain of the Schema asset>"
        	}
        }
        

      • To specify the full name and domain ID of a parent asset, use the props property as follows:
        

        {
        	"nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}],
        	"parent": {"name": "TB1", "type": "Table"},
        	"props": {
        		"fullname": "<full name of the Table asset>",
        		"domain_id": "<domain of the Table asset>"
        		}
        }

      • To specify the full name and domain ID of a leaf asset, use the props property as follows:
        

        {
        	"nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}],
        	"parent": {"name": "TB1", "type": "Table"},
        	"leaf": {"name": "COL1", "type": "Column"},
        	"props": {
        		"fullname": "<full name of the Column asset>",
        		"domain_id": "<domain of the Column asset>"
        		}
        }

      Show me how to find the full name and domain ID of an asset

      There are two ways to find this information.

      Via API

      You can use the Find assets API, as documented in the Collibra Developer Portal. In the body of the response, look for the following details in the results array:

      • name: This is the full name of the asset.
      • domain > id: This is the unique reference ID of the domain in which the asset is located.

      Via Data Catalog

      • To find the full name, open the relevant asset page, and then click Actions > Edit. The Edit dialog box appears. The full name is shown in the Name field.
      • To find the domain ID, open the relevant domain in Collibra. In the following example URL, the reference ID is in bold:
        https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001.

      Lineage files

      You can have one or more lineage files in the folder. The names of your lineage files have to follow the format lineage<something-unique>.json.

      You use the lineage file to define the lineage relation between two or more data objects. The lineage relations are shown as edges in the technical lineage graph. The edges represent the data flow from a source to a target.

      This section contains the path from a source to a target and defines the transformation code or transformation references to be processed by the Collibra Data Lineage service.

      Note  If the useCollibraSystemName property in your lineage harvester configuration file is set to true, the system data object is used to stitch to the System asset in Data Catalog. If the useCollibraSystemName property is set to false in your lineage harvester configuration file, do not specify the system data object in these files, or else stitching will fail.

      Tip 

      View the JSON schema for lineage files

      {
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "$defs": {
          "assetData": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              },
              "type": {
                "type": "string"
              }
            },
            "required": [
              "name",
              "type"
            ]
          },
          "props": {
            "type": ["object", "null"],
            "properties": {
              "fullname": {
                "type": "string"
              },
              "domain_id": {
                "type": "string"
              }
            },
            "required": [
              "fullname"
            ]
          }
        },
        "type": "object",
        "properties": {
          "src": {
            "anyOf": [
              {
                "type": "object",
                "properties": {
                  "nodes": {
                    "type": "array",
                    "items": {
                      "$ref": "#/$defs/assetData"
                    }
                  },
                  "parent": {
                    "$ref": "#/$defs/assetData"
                  },
                  "leaf": {
                    "$ref": "#/$defs/assetData"
                  },
                  "props": {
                    "$ref": "#/$defs/props"
                  }
                },
                "required": [
                  "nodes",
                  "parent",
                  "leaf"
                ]
              },
              {
                "type": "object",
                "properties": {
                  "nodes": {
                    "type": "array",
                    "items": {
                      "$ref": "#/$defs/assetData"
                    }
                  },
                  "parent": {
                    "$ref": "#/$defs/assetData"
                  },
                  "props": {
                    "$ref": "#/$defs/props"
                  }
                },
                "required": [
                  "nodes",
                  "parent"
                ]
              }
            ]
          },
          "trg": {
            "anyOf": [
              {
                "type": "object",
                "properties": {
                  "nodes": {
                    "type": "array",
                    "items": {
                      "$ref": "#/$defs/assetData"
                    }
                  },
                  "parent": {
                    "$ref": "#/$defs/assetData"
                  },
                  "leaf": {
                    "$ref": "#/$defs/assetData"
                  },
                  "props": {
                    "$ref": "#/$defs/props"
                  }
                },
                "required": [
                  "nodes",
                  "parent",
                  "leaf"
                ]
              },
              {
                "type": "object",
                "properties": {
                  "nodes": {
                    "type": "array",
                    "items": {
                      "$ref": "#/$defs/assetData"
                    }
                  },
                  "parent": {
                    "$ref": "#/$defs/assetData"
                  },
                  "props": {
                    "$ref": "#/$defs/props"
                  }
                },
                "required": [
                  "nodes",
                  "parent"
                ]
              }
            ]
          },
          "source_code": {
            "type": "object",
            "properties": {
              "path": {
                "type": "string"
              },
              "highlights": {
                "type": ["array", "null"],
                "items": {
                  "type": "object",
                  "properties": {
                    "start": {
                      "type": "integer"
                    },
                    "len": {
                      "type": "integer"
                    }
                  },
                  "required": [
                    "len",
                    "start"
                  ]
                }
              }
            },
            "required": [
              "path"
            ]
          }
        },
        "required": [
          "src",
          "trg"
        ]
      }

      Example 

      [
        {
          "src": {
            "nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}],
            "parent": {"name": "TB1", "type": "Table"},
            "leaf": {"name": "COL1", "type": "Column"},
            "props": {
      	  "fullname": "<full name of the leaf asset>",
      	  "domain_id": "<domain of the leaf asset>"
      	  },
          },
          "trg": {
            "nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}],
            "parent": {"name": "TB2", "type": "Table"},
            "props": {
      	  "fullname": "<full name of the parent asset>",
      	  "domain_id": "<domain of the parent asset>"
          },
          "source_code" : {
            "path": "<folder name>/sc1.sql", 
            "highlights": [{"start": 71, "len": 69 }, ...],
            "transformation_display_name": "middle bubble"
          }
        }
       }
      ]
      

      Properties	Description
      src	The hierarchical path to the source data object. This property represents where the data comes from for a transformation. Important The source of a lineage can only be a parent or a leaf. Example  { "src": { "nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}], "parent": {"name": "TB1", "type": "Table"}, "leaf": {"name": "COL1", "type": "Column"} }
      trg	The hierarchical path to the target data object. This property represents where the data flows to. Important The target can be a parent or a leaf; however, if the source is a parent, the target must be a parent. Tip If the target asset is a parent asset and the source asset is a leaf asset, we refer to the lineage as "indirect lineage". If the target asset is a parent asset and the source asset is a parent asset, we refer to the lineage as "table-level lineage". Example  { "trg": { "nodes": [{"name":"DB1", "type": "Database"}, {"name": "SCH1", "type": "Schema"}], "parent": {"name": "TB2", "type": "Table"} }
      props	An optional property that allows you to specify the full name and domain of an asset, for the purpose of stitching. This property is not required for Database, Schema, Table and Column asset types. A word about file processing order and inadvertently specifying the same asset more than once Assets files and lineage files are processed in the following order: first, all assets files in alphabetical order, followed by all lineage files in alphabetical order. If you choose to specify props for an asset, we recommend that you do so in either an assets file or a lineage file; not both. For any asset that is inadvertently defined more than once, the first occurrence, with respect to the processing order, is the occurrence that is used. In other words: If you inadvertently define a single asset, with props, in both an assets file and a lineage file, the props values in the assets file are used. If you inadvertently define a single asset, with props, more than once in a single assets file, or in multiple assets files, the first occurrence of the asset, with respect to the processing order, is used along with the props values defined for that occurrence of the asset.
      source_code	The transformation code that determines how the technical lineage is constructed. This can be a descriptive string or a SQL statement that manipulates data. This section is optional.
      path	The path and name of the source code file that contains the transformation code. The path relative to the source_codes folder, which is in the same folder as the lineage JSON files.
      highlights	This optional property identifies a string of transformation code in a source code file to be highlighted in the source code pane at the bottom part of the technical lineage graph. The entire lines that include the transformation code are highlighted. The string must be a subset of the string of transformation code that is defined by the start and len properties.
      start	The start position of the string of the transformation code to be highlighted. The start position is in characters, not bytes.
      len	The length of the string of the transformation code to be highlighted. The length is in characters, not bytes.
      transformation_display_name	The name of the transformation when looking at the transformations view in the technical lineage viewer.

      Source codes subfolder and files

      You can provide a subfolder of source code files that define the transformation details. The source code folder and your JSON files must be in the CUSTOM_LINEAGE folder, along with the JSON files. If it's not, an error occurs indicating that the lineage harvester cannot find the source code files.

      The source code paths are relative to the CUSTOM_LINEAGE folder.

      Example 

      • source_codes/sc1.sql
      • source_codes/another-subfolder/sc2.sql

      What happens if I choose not to provide source code files?

      If you are using the lineage harvester and there are no source code files to analyze, the batch stats are empty, as shown below. The lineage relations are still created, but because batch stats are directly linked to the source codes, if source code files are not provided, this is expected.
      

      Batch stats:
      	Parsing errors: 0
      	Analysis errors: 0
      	Done: 1

      The Done: 1 result is a dummy entry, so that the source appears in the Sources tab page.
      

      Example JSON files

      For some example JSON files, go to Custom technical lineage JSON file examples.

      Example batch-definition JSON files

      In this section, we provide three detailed examples of how to configure your metadata, assets and lineage JSON files for the batch definition option.

      Example 1 is the least complex. It shows a configuration for working with data sources that conform to the traditional (System) > Database > Schema > Table > Column hierarchy. Examples 2 and 3 are more complex examples.

      Helpful considerations to keep in mind

      • Don't use asset files in the following scenarios:

        • Your data source consists of the traditional (System) > Database > Schema > Table > Column asset types and hierarchy. In that case, full names are automatically, correctly constructed.
        • You are working with assets that are not part of that traditional asset hierarchy (in which case, you need to use the props property to achieve stitching) and you define props in one or more lineage files.
      • Don't use the props property for the traditional (System) > Database > Schema > Table > Column hierarchy.
        
        
        Typical scenario in which you need to use the props property

        First off, let's examine why you don't need to use the props property for the traditional database > schema > table > column hierarchy. Let's say you have an assets file in which you define a leaf kind of asset:

        {
          "nodes": [{
            "name": "Snowflake",
            "type": "System"
          }, {
            "name": "DB1",
            "type": "Database"
          }, {
            "name": "PUBLIC",
            "type": "Schema"
          }],
          "parent": {
            "name": "T1",
            "type": "Table"
          },
          "leaf": {
            "name": "COL1",
            "type": "Column"
          }
        }
        

        In this case, the full name of the leaf asset (in this case a Column asset) is automatically and correctly constructed as: "snowflake>DB1>PUBLIC>T1>COL1".

        However, for the following custom hierarchy, you can use the props property to specify the correct full name of the leaf asset, in this case a File asset.

        {
        "nodes": [{
          "name": "gcs",
          "type": "GCS File System"
        }, {
          "name": "bucket1",
          "type": "GCS Bucket"
        }, {
          "name": "/",
          "type": "Directory"
        }],
        "parent": {
          "name": "examples",
          "type": "Directory"
        },
        "leaf": {
          "name": "data.xls",
          "type": "File"
        },
        "props": {
          "fullname": "gcs > bucket1/examples/data.xls",
          "domain_id": "<domain in which the file asset resides>"
        }
        

        If you don't provide the full name of the leaf asset, it will be constructed using the default traditional formatting (system) > database > schema > table > column. The result would be the full name: "gcs > bucket1 > / > examples > data.xls". However, this is not the correct construction for File assets. The full name provided in the example above ensures the correct construction, so that stitching is achieved.

      Examples

      Example 1

      Scenario

      In this example, we are working with a single data source with the traditional (System) > Database > Schema > Table > Column asset types and hierarchy. Therefore, we don't need to include an asset file or use the props property.

      Which files to include?

      We are including the following files:

      __CUSTOM-LINEAGE__
          ├── lineage.json
          ├── metadata.json
          └── source_codes
              ├── source_code_view_1.txt
              └── source_code_view_2.txt

      • A metadata JSON file.
        
        Tip You always need exactly one metadata JSON file.
      • One lineage JSON file, to define the lineage relationships and to show:
        • Column-level lineage.
        • Column-level lineage from the same source (src), which is achieved by adding another entry with the same source.
        • Indirect lineage, in other words the target (trg) is a parent asset.
        • Table-level lineage, in other words both the source and the target are a parent asset.
      • Two source code files in a source_code directory.
        
        Tip Source code files are always optional.

      The metadata JSON file

      {
        "version": 3,
        "application_name": "custom lineage batch example 1",
        "asset_types": {
          "System": {
            "uuid": "00000000-0000-0000-0000-000000031302"
          },
          "Column": {
            "uuid": "00000000-0000-0000-0000-000000031008"
          },
          "Table": {
            "uuid": "00000000-0000-0000-0000-000000031007"
          },
          "Database": {
            "uuid": "00000000-0000-0000-0000-000000031006"
          },
          "Schema": {
            "uuid": "00000000-0000-0000-0001-000400000002"
          }
        }
      }

      The lineage JSON file

      [{
          "src": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "T1",
              "type": "Table"
            },
            "leaf": {
              "name": "col1",
              "type": "Column"
            }
          },
          "trg": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "VIEW_1",
              "type": "Table"
            },
            "leaf": {
              "name": "col1",
              "type": "Column"
            }
          }
        }, {
          "src": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "T1",
              "type": "Table"
            },
            "leaf": {
              "name": "col1",
              "type": "Column"
            }
          },
          "trg": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "VIEW_1",
              "type": "Table"
            },
            "leaf": {
              "name": "col2",
              "type": "Column"
            }
          },
          "source_code": {
            "path": "source_codes/source_code_view_1.txt",
            "highlights": [{
              "start": 0,
              "len": 43
            }],
            "transformation_display_name": "view_1 creation"
          }
        }, {
          "src": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "T1",
              "type": "Table"
            },
            "leaf": {
              "name": "col2",
              "type": "Column"
            }
          },
          "trg": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "VIEW_1",
              "type": "Table"
            }
          }
        },
        {
          "src": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "T2",
              "type": "Table"
            }
          },
          "trg": {
            "nodes": [{
              "name": "snowflake",
              "type": "System"
            }, {
              "name": "DB1",
              "type": "Database"
            }, {
              "name": "PUBLIC",
              "type": "Schema"
            }],
            "parent": {
              "name": "VIEW_2",
              "type": "Table"
            }
          },
          "source_code": {
            "path": "source_codes/source_code_view_2.txt",
            "highlights": [{
              "start": 0,
              "len": 39
            }],
            "transformation_display_name": "view_2 creation"
          }
        }
      ]
      

      Example 2

      Scenario

      In this example, we are working with two data sources:

      • A source system with the following asset types and hierarchy: GCS File System > GCS Bucket > Directory > File.
      • A target system with the traditional (System) > Database > Schema > Table > Column asset types and hierarchy.

      To achieve stitching, we need to use the props property to define the correct full-name construction for the File asset in the source system. We can define props in a lineage file. By doing so, we don't need to include any asset files.

      Which files to include?

      We are including the following files:

      __CUSTOM-LINEAGE__
          ├── lineage.json
          ├── metadata.json

      • A metadata JSON file.
        
        Tip You always need exactly one metadata JSON file.
      • One lineage JSON file, with the props property, to define the correct full-name construction for the File asset in the source system and achieve stitching.
        
        Tip By defining the props in the lineage file, we don't need to include an assets file. If, for example, we had several lineage files, it would be easier to include an assets file and define the props there once, rather than define the props in each lineage file.

      We are not including source code files. They are always optional.

      The metadata JSON file

      {
        "version": 3,
        "application_name": "custom lineage batch example 2",
        "asset_types": {
          "System": {
            "uuid": "00000000-0000-0000-0000-000000031302"
          },
          "Column": {
            "uuid": "00000000-0000-0000-0000-000000031008"
          },
          "Table": {
            "uuid": "00000000-0000-0000-0000-000000031007"
          },
          "Database": {
            "uuid": "00000000-0000-0000-0000-000000031006"
          },
          "Schema": {
            "uuid": "00000000-0000-0000-0001-000400000002"
          },
          "File": {
            "uuid": "00000000-0000-0000-0000-000000031304"
          },
          "Directory": {
            "uuid": "00000000-0000-0000-0000-000000031303"
          },
          "GCS Bucket": {
            "uuid": "00000000-0000-0000-0001-002700000002"
          },
          "GCS File System": {
            "uuid": "00000000-0000-0000-0001-002700000001"
          }
        }
      }

      The lineage JSON file

      [{
        "src": {
          "nodes": [{
            "name": "gcs",
            "type": "GCS File System"
          }, {
            "name": "catingestiontest",
            "type": "GCS Bucket"
          }, {
            "name": "/",
            "type": "Directory"
          }, {
            "name": "ingestion-test",
            "type": "Directory"
          }],
          "parent": {
            "name": "ingestion copy",
            "type": "Directory"
          },
          "leaf": {
            "name": "mytest.csv",
            "type": "File"
          },
          "props": {
            "fullname": "f13bf705-13a4-44c9-843e-f341feccfb6e > catingestiontest/ingestion-test/ingestion copy/mytest.csv/1611609340099809",
            "domain_id": "fea1b0b0-705f-4e0d-b5eb-1f21132cc718"
          }
        },
        "trg": {
          "nodes": [{
            "name": "snowflake",
            "type": "System"
          }, {
            "name": "DB1",
            "type": "Database"
          }, {
            "name": "PUBLIC",
            "type": "Schema"
          }],
          "parent": {
            "name": "T1",
            "type": "Table"
          },
          "leaf": {
            "name": "col1",
            "type": "Column"
          }
        }
      }]
      

      Example 3

      Scenario

      In this example, we are working with the same two data sources as in Example 2:

      • A source system with the following asset types and hierarchy: GCS File System > GCS Bucket > Directory > File.
      • A target system with the traditional (System) > Database > Schema > Table > Column asset types and hierarchy.

      To achieve stitching, we need to use the props property to define the correct full-name construction for the File asset in the source system. However, this time we have multiple lineage files. Instead of defining props in each lineage file, let's include an asset file. That way we only have to define props there once.

      Which files to include?

      We are including the following files:

      __CUSTOM-LINEAGE__
          ├── assets.json
          ├── lineage-1.json
          ├── lineage-2.json
          ├── metadata.json

      • A metadata JSON file.
        
        Tip You always need exactly one metadata JSON file.
      • An assets JSON file, in which provide the list of data objects we want to include in the technical lineage, and define props .
      • Two lineage JSON files, to define the lineage relationships.
        

      We are not including source code files. They are always optional.

      Metadata JSON file

      {
        "version": 3,
        "application_name": "custom lineage batch example 2",
        "asset_types": {
          "System": {
            "uuid": "00000000-0000-0000-0000-000000031302"
          },
          "Column": {
            "uuid": "00000000-0000-0000-0000-000000031008"
          },
          "Table": {
            "uuid": "00000000-0000-0000-0000-000000031007"
          },
          "Database": {
            "uuid": "00000000-0000-0000-0000-000000031006"
          },
          "Schema": {
            "uuid": "00000000-0000-0000-0001-000400000002"
          },
          "File": {
            "uuid": "00000000-0000-0000-0000-000000031304"
          },
          "Directory": {
            "uuid": "00000000-0000-0000-0000-000000031303"
          },
          "GCS Bucket": {
            "uuid": "00000000-0000-0000-0001-002700000002"
          },
          "GCS File System": {
            "uuid": "00000000-0000-0000-0001-002700000001"
          }
        }
      }

      Assets JSON file

      [{
        "nodes": [{
          "name": "gcs",
          "type": "GCS File System"
        }, {
          "name": "catingestiontest",
          "type": "GCS Bucket"
        }, {
          "name": "/",
          "type": "Directory"
        }, {
          "name": "ingestion-test",
          "type": "Directory"
        }],
        "parent": {
          "name": "ingestion copy",
          "type": "Directory"
        },
        "leaf": {
          "name": "mytest.csv",
          "type": "File"
        },
        "props": {
          "fullname": "f13bf705-13a4-44c9-843e-f341feccfb6e > catingestiontest/ingestion-test/ingestion copy/mytest.csv/1611609340099809",
          "domain_id": "fea1b0b0-705f-4e0d-b5eb-1f21132cc718"
        }
      }, {
        "nodes": [{
          "name": "snowflake",
          "type": "System"
        }, {
          "name": "DB1",
          "type": "Database"
        }, {
          "name": "PUBLIC",
          "type": "Schema"
        }],
        "parent": {
          "name": "T1",
          "type": "Table"
        },
        "leaf": {
          "name": "col3",
          "type": "Column"
        }
      }]
      

      Lineage JSON file (1 of 2)

      [{
        "src": {
          "nodes": [{
            "name": "gcs",
            "type": "GCS File System"
          }, {
            "name": "catingestiontest",
            "type": "GCS Bucket"
          }, {
            "name": "/",
            "type": "Directory"
          }, {
            "name": "ingestion-test",
            "type": "Directory"
          }],
          "parent": {
            "name": "ingestion copy",
            "type": "Directory"
          },
          "leaf": {
            "name": "mytest.csv",
            "type": "File"
          }
        },
        "trg": {
          "nodes": [{
            "name": "snowflake",
            "type": "System"
          }, {
            "name": "DB1",
            "type": "Database"
          }, {
            "name": "PUBLIC",
            "type": "Schema"
          }],
          "parent": {
            "name": "T1",
            "type": "Table"
          },
          "leaf": {
            "name": "col1",
            "type": "Column"
          }
        }
      }]
      
      

      Lineage JSON file (2 of 2)

      [{
        "src": {
          "nodes": [{
            "name": "gcs",
            "type": "GCS File System"
          }, {
            "name": "catingestiontest",
            "type": "GCS Bucket"
          }, {
            "name": "/",
            "type": "Directory"
          }, {
            "name": "ingestion-test",
            "type": "Directory"
          }],
          "parent": {
            "name": "ingestion copy",
            "type": "Directory"
          },
          "leaf": {
            "name": "mytest.csv",
            "type": "File"
          }
        },
        "trg": {
          "nodes": [{
            "name": "snowflake",
            "type": "System"
          }, {
            "name": "DB1",
            "type": "Database"
          }, {
            "name": "PUBLIC",
            "type": "Schema"
          }],
          "parent": {
            "name": "T1",
            "type": "Table"
          },
          "leaf": {
            "name": "col2",
            "type": "Column"
          }
        }
      }]
      

21. Add a technical lineage capability to your Edge site.

    Complete the following steps to add the technical lineage capability to your Edge site.

    Prerequisites

    • You have a global role that has the System administration global permission.
    • You have a global role that has the Manage connections and capabilities global permission, for example, Edge integration engineer.

    Steps

    1. Open an Edge site.
       1. On the main toolbar, click , and then click Settings.
          The Collibra settings page opens.
       2. In the tab pane, click Edge.
          The Sites tab opens and shows a table with an overview of the Edge sites.
       3. In the table, click the name of the Edge site whose status is Healthy.
          The Edge site page opens.
    2. In the Capabilities section, click Add capability.
       The Add capability page appears.
    3. Select the relevant capability template: Technical Lineage for ADF: Technical Lineage for Databricks Unity Catalog: Technical Lineage for DataStage: Technical Lineage for Informatica Intelligent Cloud Services (IICS): Technical Lineage for Informatica PowerCenter: Technical Lineage for Matillion: Technical Lineage for SQL Server Integration Services (SSIS): Technical Lineage for dbt: Technical Lineage for dbt cloud.
       
    4. Enter the required information.

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Amazon Redshift	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Authentication Type	The authentication details for signing in to Azure Data Factory. You can select one of the following values: Service Principal When you select this authentication type, ensure that you entered the application secret for the Service Principal in the Service Principal Secret field when you created the Azure connection. Resource Owner Password Credentials When you select this authentication type, ensure that you specify the username field in this capability and also entered the password in the Service Principal Secret field when you created the Azure connection.	Yes
       ADF Connection	The Azure connection that you created.	Yes
       Username	The email address of your Azure Active Directory user. This field applies only when you selected Resource Owner Password Credentials for the Authentication Type field.	No
       Resource Group Name	The name of the resource group that the data factory belongs to.	Yes
       Subscription ID	The subscription ID of the resource group.	Yes
       Factories	The Azure Data Factory factories that Collibra Data Lineage collects and processes. Specify this property with an array of Azure Data Factory factory names. This property is optional. The following rules apply when you specify this property: Enter the factory names in square brackets ([ ]), enclose each factory name in double quotes (" "), and separate them by a comma, for example, ["MyFirstFactory", "MySecondFactory"]. The factory name is not case-sensitive. For example, the MyFactory and myfactory factories are considered the same by Azure Data Factory and Collibra Data Lineage. If you do not specify any factory name, Collibra Data Lineage collects and processes all factories that have datasets and piplelines in them.	No
       Source Configuration	The source configuration for database mapping, system mapping, schema mapping, and filtering. Specify the following properties in JSON format and enter the content in this field. If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the <sourceId>.conf file in this field. Connection definition properties Property Description Mandatory? found_dbname=<database name>;found_hostname=<server name>;found_schema=<schema name> | found_dbname=<datafactory_name>_<linkedservice_name>;found_hostname=* The information of the supported data sources in Azure Data Factory to be collected by Collibra Data Lineage. You can specify any of the following values for the found_dbname property: A database name. And then you can specify the following properties: found_hostname=<server name>, where <server name> is the name of the server that the database is running on. found_schema=<schema name>, where <schema name> is the name of the schema. This property is optional. The combination of <datafactory_name>_<linkedservice_name>, where <datafactory_name> is a data factory name and <linkedservice_name> is a linked service name. If you use this combination, specify * for the found_hostname property. Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". Yes dbname The name of the database asset in Data Catalog. Specify this property with the database name that you created when you registered the data source. No schema The name of the schema asset in Data Catalog. Specify this property with the schema name that you created when you registered the data source. If the Collibra Data Lineage fails to find the schema that you specify, it uses the default schema. No dialect If you specify a database name for the found_dbname property, select one of the following dialects. If you specify a linked service name for the found_dbname property, ignore this property. Click here for a list of dialects of supported data sources in Azure Data Factory. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for a IBM Db2 data source. generic, for any data source. greenplum, for a Greenplum data source. hana, for a SAP HANA data source. hive, for a Hive data source. impala, for a Impala data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for an PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. vertica, for a Vertica data source. No collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. If you don't specify a value for this property, DEFAULT is shown in the technical lineage. How do I configure this property if I have two databases with the same name? If you have two databases named Customers, and you created a System asset for each of these databases in Data Catalog, Customers-Europe and Customers-USA, you can configure this property as follows. "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "Customers", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "Customers-Europe" }, "found_dbname=databasename2;found_hostname=server-name.onmicrosoft.com;found_schema=schema2": { "dbname": "Customers", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "Customers-USA" }, Warning The value of this property must exactly match (including for case-sensitivity) the name of your System asset in Collibra. No Example  Show me an example <source ID> configuration file { "found_dbname=databasename1;found_hostname=server-name.onmicrosoft.com;found_schema=schema1": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" }, "found_dbname=datafactory_linkedservice;found_hostname=*": { "dbname": "linkedservice-dbname", "schema": "linkedservice-schema", "collibraSystemName": "linkedservice-system-name" } } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for ADF	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Authentication Type	The authentication details for signing in to Azure Data Factory. You can select one of the following values: Service Principal When you select this authentication type, ensure that you entered the application secret for the Service Principal in the Service Principal Secret field when you created the Azure connection. Resource Owner Password Credentials When you select this authentication type, ensure that you specify the username field in this capability and also entered the password in the Service Principal Secret field when you created the Azure connection.	Yes
       ADF Connection	The Azure connection that you created.	Yes
       Username	The email address of your Azure Active Directory user. This field applies only when you selected Resource Owner Password Credentials for the Authentication Type field.	No
       Resource Group Name	The name of the resource group that the data factory belongs to.	Yes
       Subscription ID	The subscription ID of the resource group.	Yes
       Factories	The Azure Data Factory factories that Collibra Data Lineage collects and processes. Specify this property with an array of Azure Data Factory factory names. This property is optional. The following rules apply when you specify this property: Enter the factory names in square brackets ([ ]), enclose each factory name in double quotes (" "), and separate them by a comma, for example, ["MyFirstFactory", "MySecondFactory"]. The factory name is not case-sensitive. For example, the MyFactory and myfactory factories are considered the same by Azure Data Factory and Collibra Data Lineage. If you do not specify any factory name, Collibra Data Lineage collects and processes all factories that have datasets and piplelines in them.	No
       Source Configuration	The source configuration for database mapping, system mapping, schema mapping, and filtering. Specify the following properties in JSON format and enter the content in this field. If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the connection_definitions.conf file in this field. Connection definition properties Property Description Mandatory? found_dbname=<database name>;found_hostname=<server name>;found_schema=<schema name> | found_dbname=<datafactory_name>_<linkedservice_name>;found_hostname=* The information of the supported data sources in Azure Data Factory to be collected by Collibra Data Lineage. You can specify any of the following values for the found_dbname property: A database name. And then you can specify the following properties: found_hostname=<server name>, where <server name> is the name of the server that the database is running on. found_schema=<schema name>, where <schema name> is the name of the schema. This property is optional. The combination of <datafactory_name>_<linkedservice_name>, where <datafactory_name> is a data factory name and <linkedservice_name> is a linked service name. If you use this combination, specify * for the found_hostname property. Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". Yes dbname The name of the database asset in Data Catalog. Specify this property with the database name that you created when you registered the data source. No schema The name of the schema asset in Data Catalog. Specify this property with the schema name that you created when you registered the data source. If the Collibra Data Lineage fails to find the schema that you specify, it uses the default schema. No dialect If you specify a database name for the found_dbname property, select one of the following dialects. If you specify a linked service name for the found_dbname property, ignore this property. Click here for a list of dialects of supported data sources in Azure Data Factory. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for a IBM Db2 data source. generic, for any data source. greenplum, for a Greenplum data source. hana, for a SAP HANA data source. hive, for a Hive data source. impala, for a Impala data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for an PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. vertica, for a Vertica data source. No collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. If you don't specify a value for this property, DEFAULT is shown in the technical lineage. How do I configure this property if I have two databases with the same name? If you have two databases named Customers, and you created a System asset for each of these databases in Data Catalog, Customers-Europe and Customers-USA, you can configure this property as follows. "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "Customers", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "Customers-Europe" }, "found_dbname=databasename2;found_hostname=server-name.onmicrosoft.com;found_schema=schema2": { "dbname": "Customers", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "Customers-USA" }, Warning The value of this property must exactly match (including for case-sensitivity) the name of your System asset in Collibra. No Example  Show me an example <source ID> configuration file { "found_dbname=databasename1;found_hostname=server-name.onmicrosoft.com;found_schema=schema1": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" }, "found_dbname=datafactory_linkedservice;found_hostname=*": { "dbname": "linkedservice-dbname", "schema": "linkedservice-schema", "collibraSystemName": "linkedservice-system-name" } } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Azure	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Azure	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Azure	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Custom Technical Lineage	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Databricks Connection	The Databricks connection that you created.	Yes
       Compute Resource HTTP Path	The HTTP path of the compute resource in Databricks Unity Catalog that Collibra Data Lineage collects and processes to create technical lineage. How to find the HTTP path? You can find the HTTP path in the connection details of your cluster as shown in the following graphic. For details, go to Get connection details for a cluster in Databricks documentation.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Time Frame	Specify the duration for data collection. The default value is 365, which means that Collibra Data Lineage collects the data of the past 365 days.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Save Input Metadata	This option determines whether you want to save the input metadata that is extracted from the data source in a file. The file can be useful for troubleshooting. Select this option only on request of Collibra Support.	No
       Filters	Use this section to include or exclude databases and schemas to be ingested. Enter the filters in JSON format. If you used filters when you integrated Databricks Unity Catalog, you can enter in this field the content from the Filters and Domain Mapping (Beta) field in the Databricks Unity Catalog capability. Noted that Collibra Data Lineage ignores the UUIDs that are specified in the content. For rules and a code example of specifying the filters, go to the Filters and Domain Mapping (Beta) field in the Databricks Unity Catalog capability.	No
       Logging configuration, Memory (MiB), and JVM arguments	These fields contain configuration options that can help when investigating issues with the capability. Important Only complete these fields on request of or together with Collibra Support.	No
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Databricks Unity Catalog	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Databricks Connection	The Databricks connection that you created.	Yes
       Compute Resource HTTP Path	The HTTP path of the compute resource in Databricks Unity Catalog that Collibra Data Lineage collects and processes to create technical lineage. How to find the HTTP path? You can find the HTTP path in the connection details of your cluster as shown in the following graphic. For details, go to Get connection details for a cluster in Databricks documentation.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Time Frame	Specify the duration for data collection. The default value is 365, which means that Collibra Data Lineage collects the data of the past 365 days.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Save Input Metadata	This option determines whether you want to save the input metadata that is extracted from the data source in a file. The file can be useful for troubleshooting. Select this option only on request of Collibra Support.	No
       Filters	Use this section to include or exclude databases and schemas to be ingested. Enter the filters in JSON format. If you used filters when you integrated Databricks Unity Catalog, you can enter in this field the content from the Filters and Domain Mapping (Beta) field in the Databricks Unity Catalog capability. Noted that Collibra Data Lineage ignores the UUIDs that are specified in the content. For rules and a code example of specifying the filters, go to the Filters and Domain Mapping (Beta) field in the Databricks Unity Catalog capability.	No
       Logging configuration, Memory (MiB), and JVM arguments	These fields contain configuration options that can help when investigating issues with the capability. Important Only complete these fields on request of or together with Collibra Support.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The connection definitions, where you specify relevant translations for each data source. Specify the following properties in JSON format and enter the content in this field. If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the <sourceId>.conf file in this field. Connection definition properties Property Description OdbcDataSources Open Database Connectivity data sources in IBM InfoSphere DataStage for which you want to create a technical lineage. <data-source-name> The ODBC data source name that you use in your DataStage projects. This section contains the properties to translate the database, schema and dialect. dbname The name of your database, to which the ODBC data source connection refers. schema The name of your schema, to which the ODBC data source connection refers. dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. This property is optional. NonOdbcConnectors Other data source connectors in IBM InfoSphere DataStage for which you want to create a technical lineage. For example, DB2, Oracle or Netezza. Note This section is optional. <data-source-connector-ID> The data source username and database of the connector that you use in your DataStage projects. This usually looks like for example admin@database-name. The combination of the username and database name should be unique. The following section contains the properties to translate the database, schema and dialect. dbname The name of your database, to which the data source connection refers. schema The name of your schema, to which the data source connection refers. dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. This property is optional. Jobs The jobs that you want technical lineage via Edge to collect and process to create the technical lineage. This section is optional. The following rules apply when you specify this section: Specify jobs that are executed so that the technical lineage graph does not include any job parameters with undefined values. Specify only the first and parent jobs in a sequence of executed jobs. Technical lineage via Edge automatically collects all jobs that are called by the parent jobs. For example, if you have the a sequence of jobs that include job1, job2, job3, job4, and job5, where job1 calls job2, job2 calls job3, job3 calls job5, and job4 calls job3. Specify only job1 and job4, and technical lineage via Edge collects and processes all five jobs based on the sequence. If you do not specify this section, technical lineage via Edge collects all jobs, but without proper sequencing. Therefore, some inherited parameters might not be parsed. JobParameters The runtime parameters that are not in the DSX and ENV files. You can specify multiple job parameters. name The name of the job parameter. value The value of the job parameter. Show me an example <source ID> configuration file { "OdbcDataSources": { "oracle-data-source": { "dbname": "my-oracle-database", "schema": "my-oracle-schema", "dialect": "oracle", "collibraSystemName": "my-system" }, "mssql-data-source": { "dbname": "my-mssql-database", "schema": "my-mssql-schema", "dialect": "mssql", "collibraSystemName": "my-system" } }, "NonOdbcConnectors": { "admin@database-name": { "dbname": "my-netezza-database", "schema": "my-netezza-schema", "dialect": "netezza", "collibraSystemName": "my-system" }, "admin@second-database-name": { "dbname": "my-second-netezza-database", "schema": "my-second-netezza-schema", "dialect": "netezza", "collibraSystemName": "my-system" } }, "jobs": [ "my_job_1", "my_job_2" ], "jobParameters": [ { "name": "job_parameter_name_1", "value": "job_parameter_value_1" }, { "name": "job_parameter_name_2", "value": "job_parameter_value_2" } ] } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for DataStage	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The connection definitions, where you specify relevant translations for each data source. Specify the following properties in JSON format and enter the content in this field. If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the connection_definitions.conf file in this field. Connection definition properties Property Description OdbcDataSources Open Database Connectivity data sources in IBM InfoSphere DataStage for which you want to create a technical lineage. <data-source-name> The ODBC data source name that you use in your DataStage projects. This section contains the properties to translate the database, schema and dialect. dbname The name of your database, to which the ODBC data source connection refers. schema The name of your schema, to which the ODBC data source connection refers. dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. This property is optional. NonOdbcConnectors Other data source connectors in IBM InfoSphere DataStage for which you want to create a technical lineage. For example, DB2, Oracle or Netezza. Note This section is optional. <data-source-connector-ID> The data source username and database of the connector that you use in your DataStage projects. This usually looks like for example admin@database-name. The combination of the username and database name should be unique. The following section contains the properties to translate the database, schema and dialect. dbname The name of your database, to which the data source connection refers. schema The name of your schema, to which the data source connection refers. dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. This property is optional. Jobs The jobs that you want technical lineage via Edge to collect and process to create the technical lineage. This section is optional. The following rules apply when you specify this section: Specify jobs that are executed so that the technical lineage graph does not include any job parameters with undefined values. Specify only the first and parent jobs in a sequence of executed jobs. Technical lineage via Edge automatically collects all jobs that are called by the parent jobs. For example, if you have the a sequence of jobs that include job1, job2, job3, job4, and job5, where job1 calls job2, job2 calls job3, job3 calls job5, and job4 calls job3. Specify only job1 and job4, and technical lineage via Edge collects and processes all five jobs based on the sequence. If you do not specify this section, technical lineage via Edge collects all jobs, but without proper sequencing. Therefore, some inherited parameters might not be parsed. JobParameters The runtime parameters that are not in the DSX and ENV files. You can specify multiple job parameters. name The name of the job parameter. value The value of the job parameter. Show me an example <source ID> configuration file { "OdbcDataSources": { "oracle-data-source": { "dbname": "my-oracle-database", "schema": "my-oracle-schema", "dialect": "oracle", "collibraSystemName": "my-system" }, "mssql-data-source": { "dbname": "my-mssql-database", "schema": "my-mssql-schema", "dialect": "mssql", "collibraSystemName": "my-system" } }, "NonOdbcConnectors": { "admin@database-name": { "dbname": "my-netezza-database", "schema": "my-netezza-schema", "dialect": "netezza", "collibraSystemName": "my-system" }, "admin@second-database-name": { "dbname": "my-second-netezza-database", "schema": "my-second-netezza-schema", "dialect": "netezza", "collibraSystemName": "my-system" } }, "jobs": [ "my_job_1", "my_job_2" ], "jobParameters": [ { "name": "job_parameter_name_1", "value": "job_parameter_value_1" }, { "name": "job_parameter_name_2", "value": "job_parameter_value_2" } ] } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Db2	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       dbt Connection	The dbt connection that you created.	Yes
       Environment Ids	The IDs of the environments that Collibra Data Lineage uses to download job artifacts. Enter an array of environment IDs, for example [123456, 987654]. This field is required if you do not enter a value for the Admin URL field in the dbt connection. If you enter values for both the Admin URL and Environment Ids fields, the Environment Ids field takes precedence.	No
       Source Configuration	The source configuration to reduce the amount of data objects to be downloaded and enhance the performance of CollibraData Lineage in the following ways: Filter the projects and jobs to be downloaded. Include projects and jobs to be downloaded by specifying the filter property. Specify different Collibra system names for different projects by specifying the collibraSystemNames property . Map a materialization as a view instead of a table by specifying the materializedMapping property. Specify the following properties in JSON format and enter the content in this field. Example { "collibraSystemNames":{ "projects":[ {"project_id":"654321","collibraSystemName":"SystemName"} ] }, "filter":{ "jobIds":[1234], "projectIds":[654321] }, "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } } Tip Click to copy the example to your clipboard. Connection definition properties Property Description Required? collibraSystemNames You can use this section to specify the Collibra System Name for each project. No projects This section contains the project names and the Collibra system names. No project_id Your project ID. You can find the project ID in the dbt URL right after projects. For example, if your dbt URL is https://cloud.getdbt.com/develop/54321/projects/12345 , your project_id is 12345. No collibraSystemName The system or server name of the data source. This is also the name of your System asset in Data Catalog: Specify this property with the same name as the name of the System asset that you created when you registered the data source. See an example. In this code example, the project with the 12345 project ID is stitched to the systemname1 System asset in Data Catalog. { "collibraSystemNames":{ "projects":[ {"project_id":"12345","collibraSystemName":"systemname1"} ] }, } No filter You can use this section to include projects and jobs to be downloaded. Collibra Data Lineage downloads and processes only the specified jobs and projects. See an example. In this code example, the job with the 1234 job ID and the projects with the 98 and 5678 project IDs are downloaded. { "filter": { "jobIds": [ 1234 ], "projectIds": [ 98, 5678 ] } } No jobIds The job IDs of the jobs that you want to include. Specify an integer. Do not specify a string. To get your job ID, in your dbt, select Deploy and then Jobs. Select a job and you can find your job ID in the URL. For example, if your URL is cloud.getdbt.com/deploy/65432/projects/23456/jobs/123456, 123456 is your job ID. No projectIds The project IDs of the projects that you want to include. Specify an integer. Do not specify a string. You can find the project ID in the dbt URL right after projects. For example, if your dbt URL is https://cloud.getdbt.com/develop/54321/projects/12345 , your project_id is 12345. No materializedMapping Indicates how materializations in dbt are mapped. If you do not specify this property, CollibraData Lineage maps materializations to tables by default. You can change the mapping of a materialization to view. In the following example, the ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES materialization is mapped to a view. "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } No Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the <sourceId>.conf file in this field.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for dbt Cloud	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       dbt Connection	The dbt connection that you created.	Yes
       Environment Ids	The IDs of the environments that Collibra Data Lineage uses to download job artifacts. Enter an array of environment IDs, for example [123456, 987654]. This field is required if you do not enter a value for the Admin URL field in the dbt connection. If you enter values for both the Admin URL and Environment Ids fields, the Environment Ids field takes precedence.	No
       Source Configuration	The source configuration to reduce the amount of data objects to be downloaded and enhance the performance of Collibra Data Lineage in the following ways: Filter the projects and jobs to be downloaded. Include projects and jobs to be downloaded by specifying the filter property. Specify different Collibra system names for different projects by specifying the collibraSystemNames property . Map a materialization as a view instead of a table by specifying the materializedMapping property. Specify the following properties in JSON format and enter the content in this field. Example { "collibraSystemNames":{ "projects":[ {"project_id":"654321","collibraSystemName":"SystemName"} ] }, "filter":{ "jobIds":[1234], "projectIds":[654321] }, "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } } Tip Click to copy the example to your clipboard. Connection definition properties Property Description Required? collibraSystemNames You can use this section to specify the Collibra System Name for each project. No projects This section contains the project names and the Collibra system names. No project_id Your project ID. You can find the project ID in the dbt URL right after projects. For example, if your dbt URL is https://cloud.getdbt.com/develop/54321/projects/12345 , your project_id is 12345. No collibraSystemName The system or server name of the data source. This is also the name of your System asset in Data Catalog: Specify this property with the same name as the name of the System asset that you created when you registered the data source. See an example. In this code example, the project with the 12345 project ID is stitched to the systemname1 System asset in Data Catalog. { "collibraSystemNames":{ "projects":[ {"project_id":"12345","collibraSystemName":"systemname1"} ] }, } No filter You can use this section to include projects and jobs to be downloaded. Collibra Data Lineage downloads and processes only the specified jobs and projects. See an example. In this code example, the job with the 1234 job ID and the projects with the 98 and 5678 project IDs are downloaded. { "filter": { "jobIds": [ 1234 ], "projectIds": [ 98, 5678 ] } } No jobIds The job IDs of the jobs that you want to include. Specify an integer. Do not specify a string. To get your job ID, in your dbt, select Deploy and then Jobs. Select a job and you can find your job ID in the URL. For example, if your URL is cloud.getdbt.com/deploy/65432/projects/23456/jobs/123456, 123456 is your job ID. No projectIds The project IDs of the projects that you want to include. Specify an integer. Do not specify a string. You can find the project ID in the dbt URL right after projects. For example, if your dbt URL is https://cloud.getdbt.com/develop/54321/projects/12345 , your project_id is 12345. No materializedMapping Indicates how materializations in dbt are mapped. If you do not specify this property, CollibraData Lineage maps materializations to tables by default. You can change the mapping of a materialization to view. In the following example, the ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES materialization is mapped to a view. "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } No Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the <sourceId>.conf file in this field.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The source configuration to reduce the amount of data objects to be downloaded and enhance the performance of CollibraData Lineage in the following ways: Specify the following properties in JSON format and enter the content in this field. Example { "collibraSystemNames":{ "projects":[ {"project_id":"654321","collibraSystemName":"SystemName"} ] }, "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } } Tip Click to copy the example to your clipboard. Connection definition properties Property Description Required? Collibra System Name The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source. No projects This section contains the project names and the Collibra system names. No project_id Your project ID. You can find the project ID in the first few properties of the manifest.json file. No collibraSystemName The system or server name of the data source. This is also the name of your System asset in Data Catalog: Specify this property with the same name as the name of the System asset that you created when you registered the data source. See an example. In this code example, the project with the 12345 project ID is stitched to the systemname1 System asset in Data Catalog. { "collibraSystemNames":{ "projects":[ {"project_id":"12345","collibraSystemName":"systemname1"} ] }, } No materializedMapping Indicates how materializations in dbt are mapped. If you do not specify this property, CollibraData Lineage maps materializations to tables by default. You can change the mapping of a materialization to view. In the following example, the ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES materialization is mapped to a view. "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } No	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for dbt	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The source configuration to reduce the amount of data objects to be downloaded and enhance the performance of CollibraData Lineage in the following ways: Specify the following properties in JSON format and enter the content in this field. Example { "collibraSystemNames":{ "projects":[ {"project_id":"654321","collibraSystemName":"SystemName"} ] }, "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } } Tip Click to copy the example to your clipboard. Connection definition properties Property Description Required? Collibra System Name The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source. No projects This section contains the project names and the Collibra system names. No project_id Your project ID. You can find the project ID in the first few properties of the manifest.json file. No collibraSystemName The system or server name of the data source. This is also the name of your System asset in Data Catalog: Specify this property with the same name as the name of the System asset that you created when you registered the data source. See an example. In this code example, the project with the 12345 project ID is stitched to the systemname1 System asset in Data Catalog. { "collibraSystemNames":{ "projects":[ {"project_id":"12345","collibraSystemName":"systemname1"} ] }, } No materializedMapping Indicates how materializations in dbt are mapped. If you do not specify this property, CollibraData Lineage maps materializations to tables by default. You can change the mapping of a materialization to view. In the following example, the ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES materialization is mapped to a view. "materializedMapping":{ "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW" } No	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for BigQuery	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Project ID	The ID of the project. Tip You can add extra project IDs by clicking Add property.	Yes
       Region	The location of your BigQuery data. This is the region that you specified when you create a data set. If the region that you specify here doesn't match the region you specified when you created a data set, then: The metadata of that data set will not be harvested. Metadata of the data sets in the region you specify here will be harvested. If you don't specify a region, the region is defaulted to US, meaning that metadata (and lineage) will be harvested only for datasets located in the US region.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Columns Tail This query retrieves all columns tails. Views This query retrieves the view definitions. Dataset names This query retrieves all logical units in the project. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Project ID	The ID of the project. Tip You can add extra project IDs by clicking Add property.	Yes
       Region	The location of your BigQuery data. This is the region that you specified when you create a data set. If the region that you specify here doesn't match the region you specified when you created a data set, then: The metadata of that data set will not be harvested. Metadata of the data sets in the region you specify here will be harvested. If you don't specify a region, the region is defaulted to US, meaning that metadata (and lineage) will be harvested only for datasets located in the US region.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Columns Tail This query retrieves all columns tails. Views This query retrieves the view definitions. Dataset names This query retrieves all logical units in the project. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Greenplum	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Hive	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       External Database Name	The database value to be used as the database name in the full path (system -> database -> schema -> table). Use this field to ensure successful stitching for a database-less data source. You can specify one of the following values: CData, which Cdata drivers returned as a placeholder. Use this value if you did not create a custom database name by using the CustomizedDefaultCatalogName property when you registered your data source. The custom database name that you specified for the CustomizedDefaultCatalogName property when you registered your data source. See an example When you registered a HiveQL data source on Edge and did not specify the CustomizedDefaultCatalogName property, the following full path to a column in Data Catalog is created and CData is used as the database name:  Hive_123 (system) > CData (database) > Hive_ABC (schema) > Table > Column When Collibra Data Lineage collects metadata from the HiveQL data source, the value of the Database Name field is used as the schema name because HiveQL is database-less. If you do not enter a value for the External Database Name field, the value of the Collibra System Name field is used as the database name. If you set the Collibra system name setting to true, the value of the Collibra System Name field is also used as the system name. In this case, the full path is shown as follows and does not match the full path in Data Catalog: Hive_123 (system) > Hive_123 (database) > Hive_ABC (schema) > Table > Column In this case, the stitching fails because of the mismatch of the full paths. To match the full path and preserve stitching, you must specify CData for the External Database Name field.	No
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Object Names This query retrieves a list of object names from which technical lineage can be created. The objects can include stored procedures, views, macros, and so on.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       External Database Name	The database value to be used as the database name in the full path (system -> database -> schema -> table). Use this field to ensure successful stitching for a database-less data source. You can specify one of the following values: CData, which Cdata drivers returned as a placeholder. Use this value if you did not create a custom database name by using the CustomizedDefaultCatalogName property when you registered your data source. The custom database name that you specified for the CustomizedDefaultCatalogName property when you registered your data source. See an example When you registered a HiveQL data source on Edge and did not specify the CustomizedDefaultCatalogName property, the following full path to a column in Data Catalog is created and CData is used as the database name:  Hive_123 (system) > CData (database) > Hive_ABC (schema) > Table > Column When CollibraData Lineage collects metadata from the HiveQL data source, the value of the Database Name field is used as the schema name because HiveQL is database-less. If you do not enter a value for the External Database Name field, the value of the Collibra System Name field is used as the database name. If you set the Collibra system name setting to true, the value of the Collibra System Name field is also used as the system name. In this case, the full path is shown as follows and does not match the full path in Data Catalog: Hive_123 (system) > Hive_123 (database) > Hive_ABC (schema) > Table > Column In this case, the stitching fails because of the mismatch of the full paths. To match the full path and preserve stitching, you must specify CData for the External Database Name field.	No
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Object Names This query retrieves a list of object names from which technical lineage can be created. The objects can include stored procedures, views, macros, and so on.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       IICS connection	The Informatica Intelligent Cloud Services (IICS) connection that you created. Note Collibra Data Intelligence Platform 2023.03 or newer is required to use the Informatica Intelligent Cloud Services (IICS) connection.	Yes
       Objects	The objects that you want to retrieve. Each object requires a path and a type as shown in the following example, where, path The path to the object, which is relative to the Explore directory in IICS, for example, Sales. type The type of the object, for example, Taskflow. IICS scanner's starting point is a Taskflow or Linear Taskflow (Workflow). Therefore the only meaningful types to retrieve are: Taskflow, Workflow, Project and Folder. The types are not case sensitive. Example The following example retrieves the Project, Folder, Taskflow, and Workflow objects. [ { "path" : "Sales", "type" : "Project" }, { "path" : "Finance/Task_Flows", "type" : "Folder" }, { "path" : "Common/Task_Flows/tf_CalendarDimension", "type" : "Taskflow" }, { "path" : "Common/Linear_Task_Flows/wf_StateProvinceDimension", "type" : "Workflow" } ] Tip For more information about the objects that you can retrieve and the required information, go to the Informatica documentation.	Yes
       Parameter Files	Upload a ZIP file that contains Informatica Intelligent Cloud Services parameter files. You can name the ZIP file as you prefer. Ensure that the ZIP file contains all parameter files that you want CollibraData Lineage to collect.	No
       Source Configuration	The connection definitions and system names. Specify the following properties in JSON format and enter the content in this field. Connection definitions Property Description Required? collibraSystemNames This section contains the system information for Informatica Intelligent Cloud Services. connections This section contains the system connection information. This is required to reference to the system or server of the connection. connectionName The name of the connection. The name must match the System asset name in Data Catalog for stitching. Yes collibraSystemName The system or server name of the data source. Use this property with the useCollibraSystemName property in the lineage harvester configuration file to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you create when you prepare the physical data layer in Data Catalog. If you don't prepare the physical data layer, Collibra Data Lineage cannot stitch the data objects in your technical lineage to the assets in Data Catalog. Specify this property with the same name as the name of the System asset that you created when you registered the data source. No connectionDefinitions This section contains the database, schema and dialect information for each connection in Informatica Intelligent Cloud Services. Note You can add connection information for each connection in the connections section. connectionName The name of the connection. The name must match with the name in a connection name in the connections section. This property is required. Yes databaseName The name of your database. The name must match the Database asset name in Data Catalog for stitching. Yes schemaName The name of your schema. The name must match the Schema asset name in Data Catalog for stitching. Yes dialect The dialect of the connection. Specify this property for Collibra Data Lineage to properly extract and parse queries that are related to this connection. You can enter one of the following values: bigquery db2 hana hive greenplum mssql mysql netezza oracle postgres redshift snowflake spark teradata No Example { "collibraSystemNames": { "connections": [ { "connectionName": "DG_con_standby_cmdm_clientors", "collibraSystemName": "PUBLIC" }, { "connectionName": "DG_con_dev_dg_dgiauser_su", "collibraSystemName": "PUBLIC" } ] }, "connectionDefinitions": [ { "connectionName": "DG_con_standby_cmdm_clientors", "databaseName": "main", "schemaName": "dbo", "dialect": "oracle" }, { "connectionName": "DG_con_dev_dg_dgiauser_su", "databaseName": "main", "schemaName": "dbo", "dialect": "oracle" } ] } Tip Click to copy the example to your clipboard. Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the source ID configuration file in this field.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical lineage for Informatica Intelligent Cloud Services (IICS)	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       IICS connection	The Informatica Intelligent Cloud Services (IICS) connection that you created. Note Collibra Data Intelligence Platform 2023.03 or newer is required to use the Informatica Intelligent Cloud Services (IICS) connection.	No
       Objects	The objects that you want to retrieve. Each object requires a path and a type as shown in the following example, where, path The path to the object, which is relative to the Explore directory in IICS, for example, Sales. type The type of the object, for example, Taskflow. IICS scanner's starting point is a Taskflow or Linear Taskflow (Workflow). Therefore the only meaningful types to retrieve are: Taskflow, Workflow, Project and Folder. The types are not case sensitive. Example The following example retrieves the Project, Folder, Taskflow, and Workflow objects. [ { "path" : "Sales", "type" : "Project" }, { "path" : "Finance/Task_Flows", "type" : "Folder" }, { "path" : "Common/Task_Flows/tf_CalendarDimension", "type" : "Taskflow" }, { "path" : "Common/Linear_Task_Flows/wf_StateProvinceDimension", "type" : "Workflow" } ] Tip For more information about the objects that you can retrieve and the required information, go to the Informatica documentation.	Yes
       Parameter Files	Upload a ZIP file that contains Informatica Intelligent Cloud Services parameter files. You can name the ZIP file as you prefer. Ensure that the ZIP file contains all parameter files that you want Collibra Data Lineage to collect.	No
       Source Configuration	The connection definitions and system names. Specify the following properties in JSON format and enter the content in this field. Connection definitions Property Description Required? collibraSystemNames This section contains the system information for Informatica Intelligent Cloud Services. connections This section contains the system connection information. This is required to reference to the system or server of the connection. connectionName The name of the connection. The name must match the System asset name in Data Catalog for stitching. Yes collibraSystemName The system or server name of the data source. Use this property with the useCollibraSystemName property in the lineage harvester configuration file to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you create when you prepare the physical data layer in Data Catalog. If you don't prepare the physical data layer, Collibra Data Lineage cannot stitch the data objects in your technical lineage to the assets in Data Catalog. Specify this property with the same name as the name of the System asset that you created when you registered the data source. No connectionDefinitions This section contains the database, schema and dialect information for each connection in Informatica Intelligent Cloud Services. Note You can add connection information for each connection in the connections section. connectionName The name of the connection. The name must match with the name in a connection name in the connections section. This property is required. Yes databaseName The name of your database. The name must match the Database asset name in Data Catalog for stitching. Yes schemaName The name of your schema. The name must match the Schema asset name in Data Catalog for stitching. Yes dialect The dialect of the connection. Specify this property for Collibra Data Lineage to properly extract and parse queries that are related to this connection. You can enter one of the following values: bigquery db2 hana hive greenplum mssql mysql netezza oracle postgres redshift snowflake spark teradata No Example { "collibraSystemNames": { "connections": [ { "connectionName": "DG_con_standby_cmdm_clientors", "collibraSystemName": "PUBLIC" }, { "connectionName": "DG_con_dev_dg_dgiauser_su", "collibraSystemName": "PUBLIC" } ] }, "connectionDefinitions": [ { "connectionName": "DG_con_standby_cmdm_clientors", "databaseName": "main", "schemaName": "dbo", "dialect": "oracle" }, { "connectionName": "DG_con_dev_dg_dgiauser_su", "databaseName": "main", "schemaName": "dbo", "dialect": "oracle" } ] } Tip Click to copy the example to your clipboard. Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the source ID configuration file in this field.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The connection definitions and system names. Specify the following properties in JSON format and enter the content in this field. If the connection definitions are provided but certain properties are not specified, an analyze error called CONFIGURATION is displayed in the transformations table on the Sources tab page when the technical lineage is created. The unspecified properties are marked as UNDEFINED in the analyze error. For more information about the analyze errors, go to Analyze errors and possible solutions in Technical lineage Sources tab page. Connection definitions Property Description connectionDefinitions This section contains the connection properties to a source in Informatica PowerCenter. <connectionName> The type of your source or target data source. This section contains the connection properties to a source or target in Informatica PowerCenter. Note Define a connection in the connection definitions only once; specifically, define a data source with the <connectionName> property specified only once in the connection definitions. If you define a connection multiple times, unexpected lineage and stitching issues might occur. dbname The name of your source or target database. schema The name of your source or target schema. dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. collibraSystemNames The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. This property is optional. databases This section contains the database information. This is required to connect directly to the system or server of the database. dbname The name of the database. The database name is the same as the name you entered in the <connectionName> section. collibraSystemName The system or server name of the database. connections This section contains the connection information. This is required to reference to the system or server of the connection. connectionName The name of the connection. collibraSystemName The system or server name of the connection. Important If you are using variables in Informatica PowerCenter, add the value of the variable instead of the name in the connection definitions. For example, if the parameter file contains $DBConnection_dwh=DWH_EXPORT then you add the following connection definitions: { "DWH_EXPORT": { "dbname": "DWH", "schema": "DBO" } } Example { "connectionDefinitions": { "oracle_source": { "dbname": "oracle-source-database-name1", "schema": "my Oracle source schema", "dialect": "oracle" }, "oracle_target": { "dbname": "oracle-target-database-name2", "schema": "my other oracle target schema", "dialect": "oracle" } }, "collibraSystemNames": { "databases": [ { "dbname": "oracle-source-database-name1", "collibraSystemName": "oracle-system-name1" }, { "dbname": "oracle-target-database-name2", "collibraSystemName": "oracle-system-name2" } ], "connections": [ { "connectionName": "oracle-connection-name1", "collibraSystemName": "oracle-system-name1" }, { "connectionName": "oracle-connection-name2", "collibraSystemName": "oracle-system-name2" } ] } } Tip Click to copy the example to your clipboard. Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the source ID configuration file in this field.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Informatica PowerCenter	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The connection definitions and system names. Specify the following properties in JSON format and enter the content in this field. If the connection definitions are provided but certain properties are not specified, an analyze error called CONFIGURATION is displayed in the transformations table on the Sources tab page when the technical lineage is created. The unspecified properties are marked as UNDEFINED in the analyze error. For more information about the analyze errors, go to Analyze errors and possible solutions in Technical lineage Sources tab page. Connection definitions Property Description connectionDefinitions This section contains the connection properties to a source in Informatica PowerCenter. <connectionName> The type of your source or target data source. This section contains the connection properties to a source or target in Informatica PowerCenter. Note Define a connection in the connection definitions only once; specifically, define a data source with the <connectionName> property specified only once in the connection definitions. If you define a connection multiple times, unexpected lineage and stitching issues might occur. dbname The name of your source or target database. schema The name of your source or target schema. dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. collibraSystemNames The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. This property is optional. databases This section contains the database information. This is required to connect directly to the system or server of the database. dbname The name of the database. The database name is the same as the name you entered in the <connectionName> section. collibraSystemName The system or server name of the database. connections This section contains the connection information. This is required to reference to the system or server of the connection. connectionName The name of the connection. collibraSystemName The system or server name of the connection. Important If you are using variables in Informatica PowerCenter, add the value of the variable instead of the name in the connection definitions. For example, if the parameter file contains $DBConnection_dwh=DWH_EXPORT then you add the following connection definitions: { "DWH_EXPORT": { "dbname": "DWH", "schema": "DBO" } } Example { "connectionDefinitions": { "oracle_source": { "dbname": "oracle-source-database-name1", "schema": "my Oracle source schema", "dialect": "oracle" }, "oracle_target": { "dbname": "oracle-target-database-name2", "schema": "my other oracle target schema", "dialect": "oracle" } }, "collibraSystemNames": { "databases": [ { "dbname": "oracle-source-database-name1", "collibraSystemName": "oracle-system-name1" }, { "dbname": "oracle-target-database-name2", "collibraSystemName": "oracle-system-name2" } ], "connections": [ { "connectionName": "oracle-connection-name1", "collibraSystemName": "oracle-system-name1" }, { "connectionName": "oracle-connection-name2", "collibraSystemName": "oracle-system-name2" } ] } } Tip Click to copy the example to your clipboard. Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the source ID configuration file in this field.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Matillion connection	The Matillion connection that you created. Note Collibra Data Intelligence Platform 2023.03 or newer is required to use the Matillion connection.	No
       Group Name	The name of your group in Matillion.	Yes
       Project Name	The name of your project in Matillion. You can only add the name of one project. If you want to create a technical lineage for other projects, add a technical lineage for Matillion capability for each project.	Yes
       Environment Name	The name of your environment in Matillion. You can only add the name of one environment. If you want to create a technical lineage for other environments, add a technical lineage for Matillion capability for each environment.	Yes
       Start timestamp	The timestamp of tasks in Matillion, which indicates the amount of metadata that technical lineage via Edge collects. Specify this field with a UNIX timestamp in milliseconds. The default value is 1, which gets as much history as Matillion provides. Matillion provides 7 days of history by default.	Yes
       Source Configuration	The connection definitions and system names. Specify the following properties in JSON format and enter the content in this field. Connection definitions Property Description Mandatory? found_dbname=<database name>;found_hostname=<server name> The information of the supported data sources in Matillion to be collected by Collibra Data Lineage. <database name> The database name in Matillion. <server name> The name of the server that the database is running on. You can specify found_hostname=* to include all servers. Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". Yes dbname The name of the database asset in Data Catalog. If you leave this property blank, the database is stitched to the database of DEFAULT in Data Catalog. No schema The name of the schema asset in Data Catalog. Specify this property with the schema name that you created when you registered the data source. If you leave this property blank, the schema is stitched to the schema of DEFAULT in Data Catalog. No dialect Select one of the following dialects for your data source Click here for a list of dialects of supported data sources in Matillion. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for a IBM Db2 data source. generic, for any data source. greenplum, for a Greenplum data source. hana, for a SAP HANA data source. hive, for a Hive data source. impala, for a Impala data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for an PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. vertica, for a Vertica data source. No collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. If you leave this property blank, the system is stitched to the system of DEFAULT in Data Catalog. If you are missing lineage or your lineage objects aren’t stitching to Catalog assets in Data Catalog as you expect, ensure this property is specified properly. How do I configure this property if I have two databases with the same name? For example, if you have two databases named Customers. When you register the data source, the Customers-Europe and Customers-USA system assets are created. You can then configure this property as follows. { "found_dbname=dbtest;found_hostname=test": { "dbname": "Customers", "dialect": "mssql", "collibraSystemName": "Customers-Europe" }, "found_dbname=testsid;found_hostname=*": { "dbname": "Customers", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "Customers-USA" } } Warning The value of this property must exactly match (including for case-sensitivity) the name of your System asset in Collibra. No Example { "found_dbname=dbtest;found_hostname=test": { "collibraSystemName": "mssql-system-name" }, "found_dbname=testsid;found_hostname=*": { "dbname": "oracle-database-name", "schema": "oracle-schema-name", "collibraSystemName": "oracle-system-name" } } Tip Click to copy the example to your clipboard. Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the source ID configuration file in this field.	No
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Matillion	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Matillion connection	The Matillion connection that you created. Note Collibra Data Intelligence Platform 2023.03 or newer is required to use the Matillion connection.	No
       Group Name	The name of your group in Matillion.	Yes
       Project Name	The name of your project in Matillion. You can only add the name of one project. If you want to create a technical lineage for other projects, add a technical lineage for Matillion capability for each project.	Yes
       Environment Name	The name of your environment in Matillion. You can only add the name of one environment. If you want to create a technical lineage for other environments, add a technical lineage for Matillion capability for each environment.	Yes
       Start timestamp	The timestamp of tasks in Matillion, which indicates the amount of metadata that technical lineage via Edge collects. Specify this field with a UNIX timestamp in milliseconds. The default value is 1, which gets as much history as Matillion provides. Matillion provides 7 days of history by default.	Yes
       Source Configuration	The connection definitions and system names. Specify the following properties in JSON format and enter the content in this field. Connection definitions Property Description Mandatory? found_dbname=<database name>;found_hostname=<server name> The information of the supported data sources in Matillion to be collected by Collibra Data Lineage. <database name> The database name in Matillion. <server name> The name of the server that the database is running on. You can specify found_hostname=* to include all servers. Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". Yes dbname The name of the database asset in Data Catalog. If you leave this property blank, the database is stitched to the database of DEFAULT in Data Catalog. No schema The name of the schema asset in Data Catalog. Specify this property with the schema name that you created when you registered the data source. If you leave this property blank, the schema is stitched to the schema of DEFAULT in Data Catalog. No dialect Select one of the following dialects for your data source Click here for a list of dialects of supported data sources in Matillion. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for a IBM Db2 data source. generic, for any data source. greenplum, for a Greenplum data source. hana, for a SAP HANA data source. hive, for a Hive data source. impala, for a Impala data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for an PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. vertica, for a Vertica data source. No collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. If you leave this property blank, the system is stitched to the system of DEFAULT in Data Catalog. If you are missing lineage or your lineage objects aren’t stitching to Catalog assets in Data Catalog as you expect, ensure this property is specified properly. How do I configure this property if I have two databases with the same name? For example, if you have two databases named Customers. When you register the data source, the Customers-Europe and Customers-USA system assets are created. You can then configure this property as follows. { "found_dbname=dbtest;found_hostname=test": { "dbname": "Customers", "dialect": "mssql", "collibraSystemName": "Customers-Europe" }, "found_dbname=testsid;found_hostname=*": { "dbname": "Customers", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "Customers-USA" } } Warning The value of this property must exactly match (including for case-sensitivity) the name of your System asset in Collibra. No Example { "found_dbname=dbtest;found_hostname=test": { "collibraSystemName": "mssql-system-name" }, "found_dbname=testsid;found_hostname=*": { "dbname": "oracle-database-name", "schema": "oracle-schema-name", "collibraSystemName": "oracle-system-name" } } Tip Click to copy the example to your clipboard. Tip If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the source ID configuration file in this field.	No
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical lineage for MicroStrategy	Yes
       Main Properties	The required information for creating a technical lineage.
       Source ID	The name of the data source. You can give this any name, as long as it is unique. Warning If you are switching between the lineage harvester and Edge, the value in this field must exactly match the value of the id property in your lineage harvester configuration file. We highly recommend that you specify only one source ID per MicroStrategy Intelligence Server.	Yes
       MicroStrategy connection	The MicroStrategy connection that you created for ingestion in Data Catalog. Tip Select the name that you provided in the Name field when you created a connection to MicroStrategy.	Yes
       Domain ID	The unique reference ID of the domain in Collibra Data Intelligence Platform in which you want to ingest the MicroStrategy assets. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.	Yes
       URL for reports	This optional property ensures that the correct URL to data objects in MicroStrategy is included on the asset pages of corresponding MicroStrategy assets. The required value depends on which platform you run MicroStrategy: For J2EE, use: "appUrlSuffix": "MicroStrategy/servlet/mstrWeb" For .NET, use: "appUrlSuffix": "MicroStrategy/asp/Main.aspx"	Yes
       MicroStrategy Library URL	If you are using a custom URL to connect to the MicroStrategy Library Server, use this field to specify the custom library URL. Important You only need to specify the URL if both of the following are true: You are connecting to a proxy server. You are not using the default, hardcoded URL to the MicroStrategy Library Server. Example If the URL to your MicroStrategy Library is https://collibra.microstrategy.com/MicroStrategyLibrary/api, you don't need to use this field, as that is the default, hardcoded URL. However, if the URL is something like https://collibra.microstrategy.com/MicroStrategyLibraryProd/api, then use this field and configure it as follows: "microStrategyLibraryUrl": "MicroStrategyLibraryProd"	No
       Source configuration	This field allows you to provide JSON code, to: Specify the default domain, meaning the domain in Collibra in which the corresponding assets of MicroStrategy metadata will be ingested if domain mapping is not configured. Note If you do configure domain mapping, the default domain is still the destination domain of the MicroStrategy Server asset. Optionally, specify from which MicroStrategy projects you want to ingest metadata, and into which domains you want to ingest the corresponding assets. Optionally, configure data source mapping, to map the name of a data source returned by the lineage harvester to the true name of the data source. Note Mapping doesn't work for custom SQL. If you previously integrated MicroStrategy via the lineage harvester, you can copy and paste in this field the JSON code from your MicroStrategy <source ID> configuration file. Connection definition properties Property Description Mandatory default_domain_id The domain in which you want the corresponding assets of MicroStrategy metadata to be ingested. Note If you configure filtering, only the MicroStrategy Server asset is ingested into this default domain. Yes filters This section allows you to specify: From which MicroStrategy projects you want to harvest metadata. Into which domains in Collibra you want to ingest the corresponding assets. If you don't want to filter on projects, don't include this section in your <source ID> configuration file. No domainId The unique resource ID of the domain (or domains) in Collibra in which you want to ingest the MicroStrategy assets. Tip If you use a filters section, you must include the domainId property in the section. If, by chance, you want to filter on certain projects, but you want to ingest all assets into the default domain, then the value of the domainId property must match the value of the default_domain_id property. Show me an example "default_domain_id": "1234567890", "filters": [ { "domainId": "1234567890", "projectNames": ["MicroStrategy Tutorial","Testing_MSTR"] }, How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold. No projectIds The IDs of the MicroStrategy projects from which you want to ingest metadata. No projectNames The project names of the MicroStrategy projects from which you want to ingest metadata. No datasourceMapping This optional section allows you to configure data source mapping. Include this section only if you need to differentiate between multiple data sources that have the same name. Note Mapping doesn't work for custom SQL. No found_datasource The name of the data source that was returned by the lineage harvester, as shown in the technical lineage. Note The data source name is case-sensitive. Yes found_project The name of the project in which the data source information resides. You can specify an asterisk (*) to search for data source information across all projects. Yes mapping Use this section to map the data source name that was returned by the lineage harvester to the true name of the data source. Example You have a Redshift data source named "RD_pearl", but the lineage harvester has returned the name "Redshift_connection". You can configure the datasourceMapping section as follows: { "datasourceMapping": [ { "found_datasource": "REDSHIFT", "found_project": "*", "mapping": { "dbname": "RD_pearl", "collibraSystemName": "TV_dev" } } ] } Yes dbname The name of the database to which you want to map the found data source. Yes schema The name of the schema in MicroStrategy. No dialect The dialect of the data source in MicroStrategy. No collibraSystemName The system or server name of a database. If you set the useCollibraSystemName property to true in your lineage harvester configuration file, but you either don't create a <source ID> configuration file, or don't specify a value for the collibraSystemName property in your <source ID> configuration file, the system name in the technical lineage is "DEFAULT". If you set the useCollibraSystemName property to false in your lineage harvester configuration file, leave this property empty as follows: "collibraSystemName": "". How do I configure this property if I have two databases with the same name? Let's assume that you have a data source named Customers. You use this data source connection in two different projects, Project_A and Project_B, but they are actually two different databases. When you prepare the physical data layer in Data Catalog, you create a System asset for each of these databases. Let's say you named them Customers-North and Customers-South. You can then configure this property as follows. "datasourceMapping": [ { "found_datasource": "Customers", "found_project": "Project_A", "mapping": { "dbname": "Customers", "collibraSystemName": "Customers_North" } }, { "found_datasource": "Customers", "found_project": "Project_B", "mapping": { "dbname": "Customers", "collibraSystemName": "Customers_South" } } ] Warning The values of this property must exactly match the name of your System asset in Collibra. Yes Example  See an example with filtering. { "default_domain_id": "66ab7911-d84a-43d6-b9f7-40130jd84ds98", "filters": [ { "domainId": "3ae946ec-9030-46b8-ad86-a217b8f99bab", "projectIDs": ["3FF7CF7D4C5A2AEBF14D8B9802698B27"] }, { "domainId": "21cfb3ae-0616-478e-9060-114130540be5", "projectNames": ["Human Resources Analysis Module"] } ], "datasourceMapping": [ { "found_datasource": "REDSHIFT", "found_project": "*", "mapping": { "dbname": "RD_pearl", "schema": "Default_North", "dialect": "spark", "collibraSystemName": "TV_dev" } } ] } Tip Click to copy the example to your clipboard.	No
       Custom Properties	This section identifies to which Collibra Data Lineage service instance you want to upload the MicroStrategy metadata. Warning This applies only for Collibra Cloud for Government customers.
       techlinKey	The unique API key to connect to the Collibra Data Lineage service instance. A unique user key is needed for each Collibra environment. If you're not sure what your user key is, please contact your Collibra Customer Success Manager. Warning This applies only for Collibra Cloud for Government customers.	No
       techlinHost	The URL of he Collibra Data Lineage service instance to which you want to upload Tableau metadata, for example "techlin-gcp-eu.collibra.com". Warning This applies only for Collibra Cloud for Government customers.	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	No
       Maximum parallel requests	This optional property allows you to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. The default value is "1", which means that HTTP requests are run in a synchronous manner, instead of in parallel. As value of "5", for example, means that as many as 5 HTTP requests can take place in parallel. A lower value reduces the chances of experiencing HTTP 401 Unauthorized errors.	No

       Field	Description	Required
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. You can give this any name, as long as it is unique. Warning If you are switching between the lineage harvester and Edge, the value in this field must exactly match the value of the id property in your lineage harvester configuration file. We highly recommend that you specify only one source ID per MicroStrategy Intelligence Server.	Yes
       MicroStrategy connection	The MicroStrategy connection that you created for ingestion in Data Catalog. Tip Select the name that you provided in the Name field when you created a connection to MicroStrategy.	Yes
       Domain ID	The unique reference ID of the domain in Collibra Data Intelligence Platform in which you want to ingest the MicroStrategy assets. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.	Yes
       URL for reports	This optional property ensures that the correct URL to data objects in MicroStrategy is included on the asset pages of corresponding MicroStrategy assets. The required value depends on which platform you run MicroStrategy: For J2EE, use: "appUrlSuffix": "MicroStrategy/servlet/mstrWeb" For .NET, use: "appUrlSuffix": "MicroStrategy/asp/Main.aspx"	Yes
       MicroStrategy Library URL	If you are using a custom URL to connect to the MicroStrategy Library Server, use this field to specify the custom library URL. Important You only need to specify the URL if both of the following are true: You are connecting to a proxy server. You are not using the default, hardcoded URL to the MicroStrategy Library Server. Example If the URL to your MicroStrategy Library is https://collibra.microstrategy.com/MicroStrategyLibrary/api, you don't need to use this field, as that is the default, hardcoded URL. However, if the URL is something like https://collibra.microstrategy.com/MicroStrategyLibraryProd/api, then use this field and configure it as follows: "microStrategyLibraryUrl": "MicroStrategyLibraryProd"	No
       Source configuration	This field allows you to provide JSON code, to: Specify the default domain, meaning the domain in Collibra in which the corresponding assets of MicroStrategy metadata will be ingested if domain mapping is not configured. Note If you do configure domain mapping, the default domain is still the destination domain of the MicroStrategy Server asset. Optionally, specify from which MicroStrategy projects you want to ingest metadata, and into which domains you want to ingest the corresponding assets. Optionally, configure data source mapping, to map the name of a data source returned by the lineage harvester to the true name of the data source. Note Mapping doesn't work for custom SQL. If you previously integrated MicroStrategy via the lineage harvester, you can copy and paste in this field the JSON code from your MicroStrategy<source ID> configuration file. Connection definition properties Property Description Mandatory default_domain_id The domain in which you want the corresponding assets of MicroStrategy metadata to be ingested. Note If you configure filtering, only the MicroStrategy Server asset is ingested into this default domain. Yes filters This section allows you to specify: From which MicroStrategy projects you want to harvest metadata. Into which domains in Collibra you want to ingest the corresponding assets. If you don't want to filter on projects, don't include this section in your <source ID> configuration file. No domainId The unique resource ID of the domain (or domains) in Collibra in which you want to ingest the MicroStrategy assets. Tip If you use a filters section, you must include the domainId property in the section. If, by chance, you want to filter on certain projects, but you want to ingest all assets into the default domain, then the value of the domainId property must match the value of the default_domain_id property. Show me an example "default_domain_id": "1234567890", "filters": [ { "domainId": "1234567890", "projectNames": ["MicroStrategy Tutorial","Testing_MSTR"] }, How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold. No projectIds The IDs of the MicroStrategy projects from which you want to ingest metadata. No projectNames The project names of the MicroStrategy projects from which you want to ingest metadata. No datasourceMapping This optional section allows you to configure data source mapping. Include this section only if you need to differentiate between multiple data sources that have the same name. Note Mapping doesn't work for custom SQL. No found_datasource The name of the data source that was returned by the lineage harvester, as shown in the technical lineage. Note The data source name is case-sensitive. Yes found_project The name of the project in which the data source information resides. You can specify an asterisk (*) to search for data source information across all projects. Yes mapping Use this section to map the data source name that was returned by the lineage harvester to the true name of the data source. Example You have a Redshift data source named "RD_pearl", but the lineage harvester has returned the name "Redshift_connection". You can configure the datasourceMapping section as follows: { "datasourceMapping": [ { "found_datasource": "REDSHIFT", "found_project": "*", "mapping": { "dbname": "RD_pearl", "collibraSystemName": "TV_dev" } } ] } Yes dbname The name of the database to which you want to map the found data source. Yes schema The name of the schema in MicroStrategy. No dialect The dialect of the data source in MicroStrategy. No collibraSystemName The system or server name of a database. If you set the useCollibraSystemName property to true in your lineage harvester configuration file, but you either don't create a <source ID> configuration file, or don't specify a value for the collibraSystemName property in your <source ID> configuration file, the system name in the technical lineage is "DEFAULT". If you set the useCollibraSystemName property to false in your lineage harvester configuration file, leave this property empty as follows: "collibraSystemName": "". How do I configure this property if I have two databases with the same name? Let's assume that you have a data source named Customers. You use this data source connection in two different projects, Project_A and Project_B, but they are actually two different databases. When you prepare the physical data layer in Data Catalog, you create a System asset for each of these databases. Let's say you named them Customers-North and Customers-South. You can then configure this property as follows. "datasourceMapping": [ { "found_datasource": "Customers", "found_project": "Project_A", "mapping": { "dbname": "Customers", "collibraSystemName": "Customers_North" } }, { "found_datasource": "Customers", "found_project": "Project_B", "mapping": { "dbname": "Customers", "collibraSystemName": "Customers_South" } } ] Warning The values of this property must exactly match the name of your System asset in Collibra. Yes Example  See an example with filtering. { "default_domain_id": "66ab7911-d84a-43d6-b9f7-40130jd84ds98", "filters": [ { "domainId": "3ae946ec-9030-46b8-ad86-a217b8f99bab", "projectIDs": ["3FF7CF7D4C5A2AEBF14D8B9802698B27"] }, { "domainId": "21cfb3ae-0616-478e-9060-114130540be5", "projectNames": ["Human Resources Analysis Module"] } ], "datasourceMapping": [ { "found_datasource": "REDSHIFT", "found_project": "*", "mapping": { "dbname": "RD_pearl", "schema": "Default_North", "dialect": "spark", "collibraSystemName": "TV_dev" } } ] } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	No
       Maximum parallel requests	This optional property allows you to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. The default value is "1", which means that HTTP requests are run in a synchronous manner, instead of in parallel. As value of "5", for example, means that as many as 5 HTTP requests can take place in parallel. A lower value reduces the chances of experiencing HTTP 401 Unauthorized errors.	No
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for MySQL	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Netezza	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Oracle	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Database Links This query retrieves links to other databases. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Materialized Views This query retrieves materialized view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Database Links This query retrieves links to other databases. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Materialized Views This query retrieves materialized view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for PostgreSQL	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog. Important This field is mandatory, but the value you specify is not taken into consideration. We will remove this field in a future Collibra version.	Yes
       Database Name Override	We strongly recommend that you not edit the full name of your System, Database and Schema assets in Data Catalog. Doing so can lead to errors during the technical lineage creation process. If stitching is missing specifically because you edited the full name of your Database asset, you can use this field to specify the current name of your Database asset in Data Catalog.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical lineage for Power BI	Yes
       Main Properties	The required custom properties are based on the selected capability template.
       Source ID	The name of the data source. You can give this any name, as long as it is unique. Warning If you are switching between the lineage harvester and Edge, the value in this field must exactly match the value of the id property in your lineage harvester configuration file. We highly recommend that you specify only one source ID per tenant.	Yes
       Power BI connection	The Power BI connection that you created for ingestion in Data Catalog. Tip Select the name that you provided in the Name field when you created a connection to Power BI.	Yes
       API URL	The API URL of your Power BI service. The default value is https://api.powerbi.com. Important This property is only relevant for US government or national cloud Power BI customers, in which case you must include and specify values for both this property and the scope property. For complete information, consult Microsoft's documentation on Power BI for US government customers.	No
       Scope	Optional property that is intended only for customers with a different scope, such as Chinese tenants. Example https://analysis.chinacloudapi.cn/powerbi/api/.default Important If you are a US government or national cloud Power BI customer, you must include and specify values for both this property and the apiUrl property. For complete information, consult Microsoft's documentation on Power BI for US government customers.	No
       Domain ID	The unique reference ID of the domain in Collibra Data Intelligence Platform in which you want to ingest the Power BI assets. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.	Yes
       Source configuration	This field allows you to provide JSON code for database mapping, workspace filtering and specifying the name of a System asset in Collibra. Map the names of the server, database and schema that were collected by the lineage harvester to their true names. Note Mapping doesn't work for custom SQL. Configure workspace filtering. Tip We highly recommend that you read through Filtering Power BI workspaces for important information and guidance before configuring your filters. If useCollibraSystemName in the lineage harvester configuration file is set to true, use the collibraSystemName property to specify the system name of databases in Power BI. Collibra Data Lineage uses the system names to match the structure of databases in Power BI to assets in Data Catalog. If you previously integrated Power BI via the lineage harvester, you can copy and paste in this field the JSON code from your Power BI <source ID> configuration file. Connection definition properties Property Description Mandatory? found_dbname=<database name>;found_hostname=<server name>;found_schema=<schema name> The database information of supported data sources in Power BI that is typically collected by the lineage harvester. Specify the name of the database (found_dbname), on which server a database is running (found_hostname), and optionally, the name of the schema (found_schema). You then use the child properties to map the names collected by the lineage harvester to the true names. Important Schema mapping is available for schemas that come from Power Query connections. It is not available, however, if a Power Query connection is created with SQL (or MDX) statements and the schema is specified in those statements. Important The keys that you specify must be unique. Show me an example of a duplicate key that would result in an error The following configuration would result in an error, becausee the key found_dbname=databasename1;found_hostname=*;found_schema=schema1 is specified twice. { "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" }, "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "oracle-database-name", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "oracle-system-name" }, "filters":[ { "domainId": "<domain-ref-id>", "description": "FirstFilter", "workspaceNames": ["*"], "excludeWorkspaceIds": ["workspaceC", "workspaceD"] }, { "domainId": "<domain-ref-id>", "description": "SecondFilter", "workspaceNames": ["workspace3", "workspace4"], "capacityIds": ["id1","id2"] } ] } Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". Yes dbname The name of the database of a supported data source in Power BI. No schema The name of the schema of a supported data source in Power BI. If the lineage harvester fails to find a specific schema, it uses the schema you specify in this property. Important Schema mapping is available for schemas that come from Power Query connections. It is not available, however, if a Power Query connection is created with SQL (or MDX) statements and the schema is specified in those statements. No dialect The dialect of the supported data source in Power BI. Click here for a list of dialects of supported data sources in Power BI. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. mssql, for a Microsoft SQL Server data source. oracle, for an Oracle data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. sybase, for a Sybase data source. No collibraSystemName The system or server name of a database. If you set the useCollibraSystemName property to true in your lineage harvester configuration file, but you either don't create a <source ID> configuration file, or don't specify a value for the collibraSystemName property in your <source ID> configuration file, the system name in the technical lineage is "DEFAULT". How do I configure this property if I have two databases with the same name? Let's assume you have two databases named Customers. When you prepare the physical data layer in Data Catalog, you create a System asset for each of these databases. Let's say you named them Customers-Europe and Customers-USA. You can then configure this property as follows. "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "Customers", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "Customers-Europe" }, "found_dbname=databasename2;found_hostname=server-name.onmicrosoft.com;found_schema=schema2": { "dbname": "Customers", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "Customers-USA" }, Warning The value of this property must exactly match (including for case-sensitivity) the name of your System asset in Collibra. Important If you are using a <source ID> configuration file for the purpose of providing the true system name of an ODBC database in Power BI, you are not required to: Set the useCollibraSystemName property in the lineage harvester configuration file to true. Specify a Collibra system name in the <source ID> configuration file. However, if the useCollibraSystemName property is set to true in the lineage harvester configuration file, then you must specify a Collibra system name in the <source ID> configuration file. Yes (unless you are using the <source ID> file to provide the true system names of ODBC databases in Power BI.) filters This section allows you to specify the Power BI workspaces from which you want to ingest metadata. The filters work as "workspace AND workspace AND capacity AND capacity", meaning that if you specify a capacity, all of the workspaces in that capacity are also ingested. Warning If you don't want to specify the Power BI workspaces from which to ingest, you must completely remove this filters section. Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". No domainId The unique resource ID of the domain (or domains), in Collibra Data Intelligence Platform, in which you want to ingest the Power BI assets. Tip You can find the domain ID by clicking the domain type. Then look in the URL of your browser to find the ID. The URL looks like https://<yourcollibrainstance>/domain/<domain ID>?<view>. Yes description Any description, as you see fit. Yes workspaceNames The names of Power BI workspaces from which you want to ingest metadata. Important Any meta-characters in the name of a workspace must be enclosed in square brackets "[ ]". For example, a workspace with the name "Sale and Marketing [automobiles]" should be formatted as follows: Sale and Marketing [[]automobiles[]] No workspaceIds The IDs of Power BI workspaces from which you want to ingest metadata. Tip We highly recommend that you read through Filtering Power BI workspaces for important information and guidance before configuring your filters. No capacityNames The names of capacities on which you want to filter. No capacityIds The IDs of capacities on which you want to filter. Warning Any letters in a capacity ID must be in upper case. No excludeWorkspaceNames The names of Power BI workspaces that you want to exclude from the ingestion job. This is useful if you want to exclude, for example, dedicated development and testing workspaces. Note The metadata of inactive and personal workspaces is not harvested or uploaded to the Collibra Data Lineage service instance. An inactive workspace is one for which no reports or dashboards have been viewed in the past 60 days. My workspace is the personal workspace for any Power BI customer to work with their own, personal content. For complete details on the advantages, limitations and configuration considerations of this property, see Filtering Power BI workspaces. No excludeWorkspaceIds The IDs of Power BI workspaces that you want to exclude from the ingestion job. This is useful if you want to exclude, for example, dedicated development and testing workspaces. For complete details on the advantages, limitations and configuration considerations of this property, see Filtering Power BI workspaces. No Example  Show me an example <source ID> configuration file { "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" }, "found_dbname=databasename2;found_hostname=server-name.onmicrosoft.com;found_schema=schema2": { "dbname": "oracle-database-name", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "oracle-system-name" }, "filters":[ { "domainId": "<domain-ref-id>", "description": "FirstFilter", "workspaceNames": ["*"], "excludeWorkspaceIds": ["workspaceC", "workspaceD"] }, { "domainId": "<domain-ref-id>", "description": "SecondFilter", "workspaceNames": ["workspace3", "workspace4"], "capacityIds": ["id1","id2"] } ] } Tip Click to copy the example to your clipboard.	No
       Custom Properties	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Metadata is harvested and uploaded in a ZIP file to a Collibra Data Lineage service instance, for processing. Use this optional property to specify whether or not the raw metadata should be deleted after it has been processed. If you select this option, the raw metadata is deleted after processing. If you don't select this option, it is stored in an Amazon S3 bucket.
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	No
       Use HTTP/1.1 protocol	Option to use HTTP/1.1 streams, in case file-size limitations are resulting in timeout errors when using the default HTTP/2 streams.	No
       Enable lineage for DAX queries (Beta)	Note This feature is not available on Collibra Cloud for Government. Option to enable DAX parsing via Collibra AI. This feature: Creates column-level lineage that includes your calculated columns and measures in Power BI. Enables stitching between calculated columns in the technical lineage and the corresponding Power BI Column assets in Data Catalog. Select this option to enable DAX parsing. Clear the checkbox to disable DAX parsing. For complete information on this feature, go to DAX parsing via Collibra AI.

       Field	Description	Required
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. You can give this any name, as long as it is unique. Warning If you are switching between the lineage harvester and Edge, the value in this field must exactly match the value of the id property in your lineage harvester configuration file. We highly recommend that you specify only one source ID per tenant.	Yes
       Power BI Connection	The Power BI connection that you created for ingestion in Data Catalog. Tip Select the name that you provided in the Name field when you created a connection to Power BI.	Yes
       API URL	The API URL of your Power BI service. The default value is https://api.powerbi.com. Important This property is only relevant for US government or national cloud Power BI customers, in which case you must include and specify values for both this property and the scope property. For complete information, consult Microsoft's documentation on Power BI for US government customers.	No
       Scope	Optional property that is intended only for customers with a different scope, such as Chinese tenants. Example https://analysis.chinacloudapi.cn/powerbi/api/.default Important If you are a US government or national cloud Power BI customer, you must include and specify values for both this property and the apiUrl property. For complete information, consult Microsoft's documentation on Power BI for US government customers.	No
       Domain ID	The unique reference ID of the domain in Collibra Data Intelligence Platform in which you want to ingest the Power BI assets. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.	Yes
       Source Configuration	This field allows you to provide JSON code for database mapping, workspace filtering and specifying the name of a System asset in Collibra. Map the names of the server, database and schema that were collected by the lineage harvester to their true names. Note Mapping doesn't work for custom SQL. Configure workspace filtering. Tip We highly recommend that you read through Filtering Power BI workspaces for important information and guidance before configuring your filters. If useCollibraSystemName in the lineage harvester configuration file is set to true, use the collibraSystemName property to specify the system name of databases in Power BI. Collibra Data Lineage uses the system names to match the structure of databases in Power BI to assets in Data Catalog. If you previously integrated Power BI via the lineage harvester, you can copy and paste in this field the JSON code from your Power BI <source ID> configuration file. Connection definition properties Property Description Mandatory? found_dbname=<database name>;found_hostname=<server name>;found_schema=<schema name> The database information of supported data sources in Power BI that is typically collected by the lineage harvester. Specify the name of the database (found_dbname), on which server a database is running (found_hostname), and optionally, the name of the schema (found_schema). You then use the child properties to map the names collected by the lineage harvester to the true names. Important Schema mapping is available for schemas that come from Power Query connections. It is not available, however, if a Power Query connection is created with SQL (or MDX) statements and the schema is specified in those statements. Important The keys that you specify must be unique. Show me an example of a duplicate key that would result in an error The following configuration would result in an error, becausee the key found_dbname=databasename1;found_hostname=*;found_schema=schema1 is specified twice. { "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" }, "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "oracle-database-name", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "oracle-system-name" }, "filters":[ { "domainId": "<domain-ref-id>", "description": "FirstFilter", "workspaceNames": ["*"], "excludeWorkspaceIds": ["workspaceC", "workspaceD"] }, { "domainId": "<domain-ref-id>", "description": "SecondFilter", "workspaceNames": ["workspace3", "workspace4"], "capacityIds": ["id1","id2"] } ] } Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". Yes dbname The name of the database of a supported data source in Power BI. No schema The name of the schema of a supported data source in Power BI. If the lineage harvester fails to find a specific schema, it uses the schema you specify in this property. Important Schema mapping is available for schemas that come from Power Query connections. It is not available, however, if a Power Query connection is created with SQL (or MDX) statements and the schema is specified in those statements. No dialect The dialect of the supported data source in Power BI. Click here for a list of dialects of supported data sources in Power BI. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. mssql, for a Microsoft SQL Server data source. oracle, for an Oracle data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. sybase, for a Sybase data source. No collibraSystemName The system or server name of a database. If you set the useCollibraSystemName property to true in your lineage harvester configuration file, but you either don't create a <source ID> configuration file, or don't specify a value for the collibraSystemName property in your <source ID> configuration file, the system name in the technical lineage is "DEFAULT". How do I configure this property if I have two databases with the same name? Let's assume you have two databases named Customers. When you prepare the physical data layer in Data Catalog, you create a System asset for each of these databases. Let's say you named them Customers-Europe and Customers-USA. You can then configure this property as follows. "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "Customers", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "Customers-Europe" }, "found_dbname=databasename2;found_hostname=server-name.onmicrosoft.com;found_schema=schema2": { "dbname": "Customers", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "Customers-USA" }, Warning The value of this property must exactly match (including for case-sensitivity) the name of your System asset in Collibra. Important If you are using a <source ID> configuration file for the purpose of providing the true system name of an ODBC database in Power BI, you are not required to: Set the useCollibraSystemName property in the lineage harvester configuration file to true. Specify a Collibra system name in the <source ID> configuration file. However, if the useCollibraSystemName property is set to true in the lineage harvester configuration file, then you must specify a Collibra system name in the <source ID> configuration file. Yes (unless you are using the <source ID> file to provide the true system names of ODBC databases in Power BI.) filters This section allows you to specify the Power BI workspaces from which you want to ingest metadata. The filters work as "workspace AND workspace AND capacity AND capacity", meaning that if you specify a capacity, all of the workspaces in that capacity are also ingested. Warning If you don't want to specify the Power BI workspaces from which to ingest, you must completely remove this filters section. Tip  You can use wildcards to capture multiple connection string combinations: Show me the supported wildcards Pattern Description * Matches everything. ? Matches any single character. [seq] Matches any character in "seq". [!seq] Matches any character not in "seq". No domainId The unique resource ID of the domain (or domains), in Collibra Data Intelligence Platform, in which you want to ingest the Power BI assets. Tip You can find the domain ID by clicking the domain type. Then look in the URL of your browser to find the ID. The URL looks like https://<yourcollibrainstance>/domain/<domain ID>?<view>. Yes description Any description, as you see fit. Yes workspaceNames The names of Power BI workspaces from which you want to ingest metadata. Important Any meta-characters in the name of a workspace must be enclosed in square brackets "[ ]". For example, a workspace with the name "Sale and Marketing [automobiles]" should be formatted as follows: Sale and Marketing [[]automobiles[]] No workspaceIds The IDs of Power BI workspaces from which you want to ingest metadata. Tip We highly recommend that you read through Filtering Power BI workspaces for important information and guidance before configuring your filters. No capacityNames The names of capacities on which you want to filter. No capacityIds The IDs of capacities on which you want to filter. Warning Any letters in a capacity ID must be in upper case. No excludeWorkspaceNames The names of Power BI workspaces that you want to exclude from the ingestion job. This is useful if you want to exclude, for example, dedicated development and testing workspaces. Note The metadata of inactive and personal workspaces is not harvested or uploaded to the Collibra Data Lineage service instance. An inactive workspace is one for which no reports or dashboards have been viewed in the past 60 days. My workspace is the personal workspace for any Power BI customer to work with their own, personal content. For complete details on the advantages, limitations and configuration considerations of this property, see Filtering Power BI workspaces. No excludeWorkspaceIds The IDs of Power BI workspaces that you want to exclude from the ingestion job. This is useful if you want to exclude, for example, dedicated development and testing workspaces. For complete details on the advantages, limitations and configuration considerations of this property, see Filtering Power BI workspaces. No Example  Show me an example <source ID> configuration file { "found_dbname=databasename1;found_hostname=*;found_schema=schema1": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" }, "found_dbname=databasename2;found_hostname=server-name.onmicrosoft.com;found_schema=schema2": { "dbname": "oracle-database-name", "schema": "oracle-schema-name", "dialect": "oracle", "collibraSystemName": "oracle-system-name" }, "filters":[ { "domainId": "<domain-ref-id>", "description": "FirstFilter", "workspaceNames": ["*"], "excludeWorkspaceIds": ["workspaceC", "workspaceD"] }, { "domainId": "<domain-ref-id>", "description": "SecondFilter", "workspaceNames": ["workspace3", "workspace4"], "capacityIds": ["id1","id2"] } ] } Tip Click to copy the example to your clipboard.	No
       Property > GovCloud	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Metadata is harvested and uploaded in a ZIP file to a Collibra Data Lineage service instance, for processing. Use this optional property to specify whether or not the raw metadata should be deleted after it has been processed. If you select this option, the raw metadata is deleted after processing. If you don't select this option, it is stored in an Amazon S3 bucket.
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	No
       Use HTTP/1.1 protocol	Option to use HTTP/1.1 streams, in case file-size limitations are resulting in timeout errors when using the default HTTP/2 streams.	No
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No
       Enable lineage for DAX queries (Beta)	Note This feature is not available on Collibra Cloud for Government. Option to enable DAX parsing via Collibra AI. This feature: Creates column-level lineage that includes your calculated columns and measures in Power BI. Enables stitching between calculated columns in the technical lineage and the corresponding Power BI Column assets in Data Catalog. Select this option to enable DAX parsing. Clear the checkbox to disable DAX parsing. For complete information on this feature, go to DAX parsing via Collibra AI.

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SAP HANA	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique. Note If you are migrating an SAP HANA data source from the lineage harvester, ensure that you run the ignore-source command with the source ID from the lineage harvester configuration file. When you synchronize this capability, an error occurs if the source ID from the lineage harvester exists even if you use the same source ID for this field. For more information, go to Migrate the technical lineage of a data source.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Views This query retrieves the view definitions. Calculated Views This query retrieves calculated views. Dependencies of Calculated Views This query retrieves dependencies of calculated views. Cross-references of Calculated Views Cross-references of Calculated Views	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       SQL Active	An option to determine whether to include or remove the technical lineage of the data source with the SQL based input. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source. If you have a capability with this option selected and the synchronization of the capability fails with the Missing required parameter hanaUseCloudScanner error message, go to In Edge Harvester, previously configured/working SAP HANA Classic capabilities fail to submit to Edge in Collibra Support Portal for a solution.	No
       Calculated Views Active	An option to determine whether to include or remove the technical lineage from calculated views in an SAP HANA Classic on-premises data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source. If you have a capability with this option selected and the synchronization of the capability fails with the Missing required parameter hanaUseCloudScanner error message, go to In Edge Harvester, previously configured/working SAP HANA Classic capabilities fail to submit to Edge in Collibra Support Portal for a solution.	No
       Use Hana Cloud	An option to determine whether to include or remove the technical lineage from calculated views in an SAP HANA Cloud/Advanced data source. To include technical lineage from the SAP HANA Cloud/Advanced data source, you must select this option and the Calculated Views Active option. Clear the checkbox to exclude the technical lineage of this data source.	No
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique. Note If you are migrating an SAP HANA data source from the lineage harvester, ensure that you run the ignore-source command with the source ID from the lineage harvester configuration file. When you synchronize this capability, an error occurs if the source ID from the lineage harvester exists even if you use the same source ID for this field. For more information, go to Migrate the technical lineage of a data source.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Views This query retrieves the view definitions. Calculated Views This query retrieves calculated views. Dependencies of Calculated Views This query retrieves dependencies of calculated views. Cross-references of Calculated Views Cross-references of Calculated Views	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       SQL Active	An option to determine whether to include or remove the technical lineage of the data source with the SQL based input. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source. If you have a capability with this option selected and the synchronization of the capability fails with the Missing required parameter hanaUseCloudScanner error message, go to In Edge Harvester, previously configured/working SAP HANA Classic capabilities fail to submit to Edge in Collibra Support Portal for a solution.	No
       Calculated Views Active	An option to determine whether to include or remove the technical lineage from calculated views in an SAP HANA Classic on-premises data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source. If you have a capability with this option selected and the synchronization of the capability fails with the Missing required parameter hanaUseCloudScanner error message, go to In Edge Harvester, previously configured/working SAP HANA Classic capabilities fail to submit to Edge in Collibra Support Portal for a solution.	No
       Use Hana Cloud	An option to determine whether to include or remove the technical lineage from calculated views in an SAP HANA Cloud/Advanced data source. To include technical lineage from the SAP HANA Cloud/Advanced data source, you must select this option and the Calculated Views Active option. Clear the checkbox to exclude the technical lineage of this data source.	No
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Snowflake	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Ingestion Method	The Snowflake ingestion methods that Collibra Data Lineage uses to ingest metadata from Snowflake data sources. Select one of the following values: SQL The SQL Snowflake ingestion mode. Collibra Data Lineage creates a column-level technical lineage based on SQL statements. SQL-API The SQL-API Snowflake ingestion mode. Collibra Data Lineage creates a column-level technical lineage based on Snowflake schemas and the access history. For more information, go to Technical lineage for Snowflake ingestion methods.	Yes
       Days	The number of days of the user access history that Collibra Data Lineage collects and processes. For example, if you set the value to 20, Collibra Data Lineage collects the last 20 days of user access history. You can use this field to limit reading from the ACCESS_HISTORY table. This field only takes effect when you use the SQL-API Snowflake ingestion mode. Specify a value in the range of 1 - 366. If you do not enter a value, all user access history is collected by default.	No
       Extra Database Definitions	The name of the database from which Collibra Data Lineage collects metadata, but the database is excluded from the technical lineage that is created. This field is useful for stitching across databases. You can specify a cross-referenced database to ensure correct lineage across all databases that Collibra Data Lineage processes to create the technical lineage. Tip You can add extra database definitions by clicking Add property.	No
       Schema Names	The schema name of your data source. This field takes effect only when you use the SQL-API Snowflake ingestion mode. You can use this field as a filter to include lineage for objects only in the specified schema. Ensure that the schema name you specify matches the Schema asset name that you created when you registered the data source in Data Catalog. Tip You can add extra schema names by clicking Add property.	No
       Source Configuration	The source configuration for the data source. Specify the following property in JSON format and enter the content in this field. This field applies only when you select the SQL-API Snowflake ingestion mode. Property Description Required? displaySampleQueries Indicates whether to display transformations with a question mark (?) or with actual values from queries in the Source code pane in the technical lineage graph. For example, you can choose to display WHERE amount < 100 or WHERE amount < ?. Specify one of the following values: true Actual values from queries are displayed. false A question mark (?) is displayed. This is the default value. No analyzeTemporaryTables Indicates whether to parse the CREATE TEMPORARY TABLE statement in the ingested queries. Specify one of the following values:  true Collibra Data Lineage examines the queries and parses the CREATE TEMPORARY TABLE statement when the following conditions are met: The query starts with the CREATE TEMPORARY TABLE statement. Collibra Data Lineage did not encounter the CREATE TEMPORARY TABLE statement before this query. false Collibra Data Lineage does not examine or parse the CREATE TEMPORARY TABLE statement in the ingested queries. This is the default value. No Example { "displaySampleQueries": true|false "analyzeTemporaryTables": true|false } Tip Click to copy the example to your clipboard.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. If you select the SQL Snowflake ingestion mode, the following queries apply: Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Views This query retrieves the view definitions. If you select the SQL-API Snowflake ingestion mode, the following queries apply: Query Description Object Dependencies This query retrieves view definitions. Columns Joined This query retrieves table and column definition information. Access History This query retrieves lineage and transformation details.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Ingestion Method	The Snowflake ingestion methods that Collibra Data Lineage uses to ingest metadata from Snowflake data sources. Select one of the following values: SQL The SQL Snowflake ingestion mode. Collibra Data Lineage creates a column-level technical lineage based on SQL statements. SQL-API The SQL-API Snowflake ingestion mode. Collibra Data Lineage creates a column-level technical lineage based on Snowflake schemas and the access history. For more information, go to Technical lineage for Snowflake ingestion methods.	Yes
       Days	The number of days of the user access history that Collibra Data Lineage collects and processes. For example, if you set the value to 20, Collibra Data Lineage collects the last 20 days of user access history. You can use this field to limit reading from the ACCESS_HISTORY table. This field only takes effect when you use the SQL-API Snowflake ingestion mode. Specify a value in the range of 1 - 366. If you do not enter a value, all user access history is collected by default.	No
       Extra Database Definitions	The name of the database from which Collibra Data Lineage collects metadata, but the database is excluded from the technical lineage that is created. This field is useful for stitching across databases. You can specify a cross-referenced database to ensure correct lineage across all databases that Collibra Data Lineage processes to create the technical lineage. Tip You can add extra database definitions by clicking Add property.	No
       Schema Names	The schema name of your data source. This field takes effect only when you use the SQL-API Snowflake ingestion mode. You can use this field as a filter to include lineage for objects only in the specified schema. Ensure that the schema name you specify matches the Schema asset name that you created when you registered the data source in Data Catalog. Tip You can add extra schema names by clicking Add property.	No
       Source Configuration	The source configuration for the data source. Specify the following property in JSON format and enter the content in this field. This field applies only when you select the SQL-API Snowflake ingestion mode. Property Description Required? displaySampleQueries Indicates whether to display transformations with a question mark (?) or with actual values from queries in the Source code pane in the technical lineage graph. For example, you can choose to display WHERE amount < 100 or WHERE amount < ?. Specify one of the following values: true Actual values from queries are displayed. false A question mark (?) is displayed. This is the default value. No analyzeTemporaryTables Indicates whether to parse the CREATE TEMPORARY TABLE statement in the ingested queries. Specify one of the following values:  true Collibra Data Lineage examines the queries and parses the CREATE TEMPORARY TABLE statement when the following conditions are met: The query starts with the CREATE TEMPORARY TABLE statement. Collibra Data Lineage did not encounter the CREATE TEMPORARY TABLE statement before this query. false Collibra Data Lineage does not examine or parse the CREATE TEMPORARY TABLE statement in the ingested queries. This is the default value. No Example { "displaySampleQueries": true|false "analyzeTemporaryTables": true|false } Tip Click to copy the example to your clipboard.	No
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. If you select the SQL Snowflake ingestion mode, the following queries apply: Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Views This query retrieves the view definitions. If you select the SQL-API Snowflake ingestion mode, the following queries apply: Query Description Object Dependencies This query retrieves view definitions. Columns Joined This query retrieves table and column definition information. Access History This query retrieves lineage and transformation details.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Spark SQL
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Select the Technical lineage capability template for your data source to create a technical lineage for the JDBC data source. Important Technical lineage via Edge is only available in private beta. Please create a support ticket to get access.	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       External Database Name	The database value to be used as the database name in the full path (system -> database -> schema -> table). Use this field to ensure successful stitching for a database-less data source. You can specify one of the following values: CData, which Cdata drivers returned as a placeholder. Use this value if you did not create a custom database name by using the CustomizedDefaultCatalogName property when you registered your data source. The custom database name that you specified for the CustomizedDefaultCatalogName property when you registered your data source. See an example When you registered a Spark SQL data source on Edge and did not specify the CustomizedDefaultCatalogName property, the following full path to a column in Data Catalog is created and CData is used as the database name:  SparkSQL_123 (system) > CData (database) > SparkSQL_ABC (schema) > Table > Column When CollibraData Lineage collects metadata from the Spark SQL data source, the value of the Database Name field is used as the schema name because Spark SQL is database-less. If you do not enter a value for the External Database Name field, the value of the Collibra System Name field is used as the database name. If you set the Collibra system name setting to true, the value of the Collibra System Name field is also used as the system name. In this case, the full path is shown as follows and does not match the full path in Data Catalog: SparkSQL_123 (system) > SparkSQL_123 (database) > SparkSQL_ABC (schema) > Table > Column In this case, the stitching fails because of the mismatch of the full paths. To match the full path and preserve stitching, you must specify CData for the External Database Name field.	No
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Object names This query retrieves a list of object names from which technical lineage can be created. The objects can include stored procedures, views, macros, and so on.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       External Database Name	The database value to be used as the database name in the full path (system -> database -> schema -> table). Use this field to ensure successful stitching for a database-less data source. You can specify one of the following values: CData, which Cdata drivers returned as a placeholder. Use this value if you did not create a custom database name by using the CustomizedDefaultCatalogName property when you registered your data source. The custom database name that you specified for the CustomizedDefaultCatalogName property when you registered your data source. See an example When you registered a Spark SQL data source on Edge and did not specify the CustomizedDefaultCatalogName property, the following full path to a column in Data Catalog is created and CData is used as the database name:  SparkSQL_123 (system) > CData (database) > SparkSQL_ABC (schema) > Table > Column When CollibraData Lineage collects metadata from the Spark SQL data source, the value of the Database Name field is used as the schema name because Spark SQL is database-less. If you do not enter a value for the External Database Name field, the value of the Collibra System Name field is used as the database name. If you set the Collibra system name setting to true, the value of the Collibra System Name field is also used as the system name. In this case, the full path is shown as follows and does not match the full path in Data Catalog: SparkSQL_123 (system) > SparkSQL_123 (database) > SparkSQL_ABC (schema) > Table > Column In this case, the stitching fails because of the mismatch of the full paths. To match the full path and preserve stitching, you must specify CData for the External Database Name field.	No
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Object names This query retrieves a list of object names from which technical lineage can be created. The objects can include stored procedures, views, macros, and so on.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SQL Server	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Database Links This query retrieves links to other databases. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Database Links This query retrieves links to other databases. Synonyms This query retrieves the alternative names for the database objects. Views This query retrieves the view definitions. Other Queries This query retrieves other data that technical lineage needs, for example stored procedures, functions, and packages.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The connection definitions, where you specify relevant translations for each data source. Specify the following properties in JSON format and enter the content in this field. If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the <source ID>.conf file in this field. Connection definition properties Property Description Required? DataSources The parent element that contains the connection definitions of your data sources in SQL Server Integration Services. If you specify the properties in this section and also the ConnStringRegExTranslation property for a data source, the connection definitions in the ConnStringRegExTranslation property takes precedence. No DataSourceName The name of your data source. No dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. No collibraSystemName The system or server name of the data source. Use this property with the useCollibraSystemName property in the lineage harvester configuration file to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you create when you prepare the physical data layer in Data Catalog. If you don't prepare the physical data layer, Collibra Data Lineage cannot stitch the data objects in your technical lineage to the assets in Data Catalog. No ConnStringRegExTranslation The parent element that opens the connection definitions. If you specify this property and also the properties in the DataSources section for a data source, the connection definitions in this property takes precedence. No <regular expression> A regular expression that must match one or more connection strings. Note  Important considerations: By default, the regular expression is not case sensitive. As a consequence, a regular expression can match with connection strings containing uppercase characters or lowercase characters. The connection string is part of the SSIS connection manager. SSIS connection managers are included in an SSIS package files (DTSX) or in connection manager files (CONMGR). Example  Regular expression: Server=sb-dhub;User ID=SYB_USER2;Initial Catalog=STAGEDB;Port=6306.* Explanation: The first section, up to .*, is a literal, but not case-sensitive, match of the characters. The dot (.) can match any single character. The asterisk (*) means zero or more of the previous, in this case any character. Match: Any connection string that starts with Server=sb-dhub;User ID=SYB_USER2;Initial Catalog=STAGEDB;Port=6306. Example: Server=sb-dhub;User ID=SYB_USER2;Initial Catalog=STAGEDB;Port=6306;Persist Security Info=True;Auto Translate=False;. No dbname The name of your database, to which the data source connection refers. No schema The name of your schema, to which the regular expression refers. No dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. No collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. No See an example { "DataSources": { "dhb-sql-prod": { "dialect": "mssql", "collibraSystemName": "my-system-name" } }, { "ConnStringRegExTranslation": { "Data Source=dhb-sql-prod;Initial Catalog=SFG_repl_staging;Provider=SQLNCLI11;Integrated Security=SSPI.*": { "dbname": "DATAHUB", "schema": "DBO", "dialect": "mssql", "collibraSystemName" : "WAREHOUSE" }, "Server=sb-dhub;User ID=SYS_USER;Initial Catalog=STAGEDB;Port=6306.*": { "dbname": "STAGEDB", "schema": "STAGE_OWNER", "dialect": "sybase", "collibraSystemName" : "" } } } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SQL Server Integration Services (SSIS)	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	Yes
       Mask	The pattern of the file names in the directory. By default, the value is *.	No
       Source Configuration	The connection definitions, where you specify relevant translations for each data source. Specify the following properties in JSON format and enter the content in this field. If you previously created a technical lineage for this data source with connection definitions by using the lineage harvester, you can enter the content from the <source ID>.conf file in this field. Connection definition properties Property Description ConnStringRegExTranslation The parent element that opens the connection definitions. <regular expression> A regular expression that must match one or more connection strings. Note  Important considerations: By default, the regular expression is not case sensitive. As a consequence, a regular expression can match with connection strings containing uppercase characters or lowercase characters. The connection string is part of the SSIS connection manager. SSIS connection managers are included in an SSIS package files (DTSX) or in connection manager files (CONMGR). Example  Regular expression: Server=sb-dhub;User ID=SYB_USER2;Initial Catalog=STAGEDB;Port=6306.* Explanation: The first section, up to .*, is a literal, but not case-sensitive, match of the characters. The dot (.) can match any single character. The asterisk (*) means zero or more of the previous, in this case any character. Match: Any connection string that starts with Server=sb-dhub;User ID=SYB_USER2;Initial Catalog=STAGEDB;Port=6306. Example: Server=sb-dhub;User ID=SYB_USER2;Initial Catalog=STAGEDB;Port=6306;Persist Security Info=True;Auto Translate=False;. dbname The name of your database, to which the data source connection refers. schema The name of your schema, to which the regular expression refers. dialect The dialect of the referenced database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. collibraSystemName The system or server name of the data source. Specify this property when you set the value of the Collibra system name setting to True to override the default Collibra System asset name for this data source. Specify this property with the same name as the name of the System asset that you created when you registered the data source. This property is optional. See an example { "DataSources": { "dhb-sql-prod": { "dialect": "mssql", "collibraSystemName": "my-system-name" } }, { "ConnStringRegExTranslation": { "Data Source=dhb-sql-prod;Initial Catalog=SFG_repl_staging;Provider=SQLNCLI11;Integrated Security=SSPI.*": { "dbname": "DATAHUB", "schema": "DBO", "dialect": "mssql", "collibraSystemName" : "WAREHOUSE" }, "Server=sb-dhub;User ID=SYS_USER;Initial Catalog=STAGEDB;Port=6306.*": { "dbname": "STAGEDB", "schema": "STAGE_OWNER", "dialect": "sybase", "collibraSystemName" : "" } } } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Sybase	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves all columns, tables, schemas, databases or projects in the form: database or project > schema > table > column. Views This query retrieves the view definitions.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical lineage for Tableau	Yes
       Main Properties	The required information for creating a technical lineage.
       Source ID	The name of the data source. You can give this any name, as long as it is unique. Warning If you are switching between the lineage harvester and Edge, the value in this field must exactly match the value of the id property in your lineage harvester configuration file. Warning You can only specify one source ID per Tableau server or Tableau online account. If you have multiple unique source IDs that refer to a single Tableau server or Tableau online account, ingestion will fail. Put another way, if you have multiple unique source IDs, each must refer to a unique Tableau server or Tableau online account.	Yes
       Tableau connection	The Tableau connection that you created for ingestion in Data Catalog. Tip Select the name that you provided in the Name field when you created a connection to Tableau.	Yes
       Domain ID	The unique reference ID of the domain in Collibra Data Intelligence Platform in which you want to ingest the Tableau assets. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.	Yes
       REST only	Indication whether or not you want to use both the Tableau REST API and Tableau Metadata API to harvest Tableau metadata. Cleared (default): The lineage harvester will use the REST API and Metadata API to harvest Tableau metadata. Selected: The lineage harvester will only use the REST API to harvest Tableau metadata. Note This filed must be cleared, to: Enable technical lineage and the automatic stitching of Column assets to Tableau Data Attribute assets. Harvest owner information for Tableau projects, workbooks and data models.	No
       Exclude images	Indication whether or not you want to excluding the downloading of images. Cleared: Images are downloaded. Selected (default): Images are not downloaded. Note The maximum number of images that can be uploaded to Collibra per day is determined by the configuration of the file upload service, in Collibra Console. For complete details, see the Upload configuration settings in DGC service configuration: options.	No
       Site ID	The site IDs of the Tableau sites that you want to include in the ingestion process. If you leave this field empty, Collibra Data Lineage will ingest the default Tableau site. To ingest from multiple Tableau sites, enter each site ID in a separate Site ID field. To ingest the default Tableau site, enter "Default" or leave the field empty. This field is not case sensitive. Warning If you enter "Default", you must include the double quotation marks. The site IDs of any other Tableau sites must not be enclosed in double quotation marks. If the formatting of the site IDs does not conform to this detail, ingestion will fail. See an example Let's say that you want to ingest from the default Tableau site and a site named "ABC". In the Site ID field, enter "Default" for the default Tableau site. Click Add property. An empty Site ID field is aded. In the new Site ID field, enter the ID of the Tableau site ABC. Tip Ensure that you specify the correct value. The correct value is the URL of the site to which you want to sign in. When you manually sign in to Tableau Server or Tableau Online, the site ID is the value that appears after /site/ in the browser address bar. In the following example URLs, the site ID is MarketingTeam: Tableau Server: http://MyServer/#/site/MarketingTeam/projects Tableau Online: https://10ay.online.tableau.com/#/site/MarketingTeam/workbooks On Tableau Server, however, the URL of the default site does not specify the site. For example, the URL for a view named Profits, on a site named Sales, is http://localhost/#/site/sales/views/profits. The URL for this same view on the default site is http://localhost/#/views/profits. The site name Sales does not figure in the URL.	No
       Site Name	The site name, or names, of the Tableau sites you specified in the Site ID field. If you don't provide a site ID in the Site ID field, in which case the default Tableau site is ingested, leave this field blank.	No
       Concurrency level	This field is intended to help if you are experiencing HTTP 401 Unauthorized errors due to too many concurrent HTTP calls, using the same token. It allows you to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. The default value is "10", meaning as many as 10 HTTP requests can take place in parallel. Consider reducing the value if you are experiencing HTTP 401 Unauthorized errors. Setting the value to "1" effectively disables the concurrency level, so that HTTP requests will be run in a synchronous manner, instead of in parallel.	No
       Source configuration	This field allows you to provide JSON code for database mapping, domain mapping and filtering. If you previously integrated Tableau via the lineage harvester, you can copy and paste in this field the JSON code from your Tableau <source ID> configuration file. Connection definition properties Property Description collibraSystemNames This section contains the system information for different Tableau data sources. Depending on the kind of data source or connection, you have to specify how to connect to this data source. Tip For more information, see the Tableau documentation. We also recommend to check the list of supported connectors in Tableau. files This section contains connection information to one or more files in Tableau. Tip If you do not have files in Tableau, you can remove this section. filePath The full path to the file. For example, the path to a JSON file. collibraSystemName The system name of the file. connectors This section contains connection information to one or more connectors in Tableau. Tip  If you do not have connectors in Tableau, you can remove this section. The values that you specify for this property are not case-sensitive. connectorUrl The URL of the connector. For example, the URL to Google Analytics. collibraSystemName The system name of the connector. cloudFiles This section contains connection information to one or more cloud files in Tableau's input data. Tip If you do not have cloud files in Tableau, you can remove this section. name The name of the file. For example, the name of a Zendesk file. collibraSystemName The system name of the cloud file. hostnameMapping This section allows you to map Tableau technical database, server and schema names to the respective real names, to preserve stitching. Warning  hostnameMapping replaces the following deprecated properties, which have been removed from this topic: The databaseMapping property. The databases sub-section of the collibraSystemNames section. hostnameMapping must not be used in combination with either of these properties. If you use the hostnameMapping section, you can still use the collibraSystemName property in conjunction with the files, connectors or cloudfiles sub-sections. Example configuration "hostnameMapping": { "found_dbname=databasename1;found_hostname=*;found_schema=test": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" } } found_dbname=<database name>;found_hostname=<server name>;found_schema=<schema name> The database information of supported data sources in Tableau that is typically collected by the lineage harvester. It allows you to specify the name of the database (found_dbname), on which server a database is running (found_hostname), and optionally, the name of the schema (found_schema). dbname The name of the database of a supported data source in Tableau. schema The name of the default schema of a supported data source in Tableau. If the lineage harvester fails to find a specific schema, it uses the default schema. dialect The dialect of the supported data source in Tableau. You don't have to specify a dialect; it will automatically be detected. If, however, you are using a dialect that is not supported, you can use this property to specify a supported dialect that is a close comparison. That way, most of your queries will be detected and processed. Show me a list of dialects of supported data sources in Tableau. redshift, for an Amazon Redshift data source. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. greenplum, for a Greenplum data source. hive, for a HiveQL data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. hana, for a SAP HANA data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. filters This section defines: From which Tableau sites and projects you want to harvest metadata. Into which domains in Collibra you want to ingest the corresponding assets. Filtering is transitive, which means that all resources in a specified project, such as Tableau workbooks and all sub-projects, are ingested. Tableau assets that are not mapped to the specified domains, for example the Tableau Server assets and the parent projects (if you specify their sub-projects), are ingested in the default domain. Important  Filtering does not affect the amount of raw metadata that is harvested from Tableau and sent to the Collibra Data Lineage service instance. Rather, it determines which metadata is ingested as assets in Data Catalog. The domainMapping and filters sections are mutually exclusive. Do not include both domainMapping and filters sections in your JSON file. Tip  If you want to ingest all of the projects in a Tableau site into multiple domains in Collibra, use the domainMapping section. If you want to ingest all of the projects in a Tableau site into the default domain, use only the domainID property in the lineage harvester configuration file. The domainID property represents the default domain. If you want to ingest all of the projects in a Tableau site into a single domain in Collibra, use site filtering. If you want to ingest metadata from only some of the projects in a Tableau site, use project filtering. You can use site filtering and project filtering together: If filtering on the same site, this "filtering" is actually domain mapping, because nothing is filtered out. The contents of the projects are ingested in the specified domains, and the rest of the contents of the site are ingested in a different, specified domain. If you are site filtering on a specific site and project filtering a different site, then site filtering is again a form of domain mapping, and the filtered projects are ingested in their specified domains. If your lineage harvester configuration file includes sites that are not mentioned in the filters section of your <source ID> configuration file, those sites are ingested in the default domain. sites The Tableau sites to be ingested and the domain in which you want to ingest metadata from the Tableau sites. Tip If you have only one Tableau site, do not include a sites section in your <source ID> file. Instead, use a projects section, to filter on Tableau projects. Include a sites section only if all of the following are true: You have more than one Tableau site. You want to ingest all of the metadata from only one Tableau site into a single domain in Collibra. The domain into which you want to ingest is not the default domain, meaning the domain specified in the domainId property in your lineage harvester configuration file. site_name: domain_id site_name The name of the site to be ingested. The site name is case-sensitive. domain_id The unique reference ID of the domain in Collibra in which you want to ingest metadata. The domain ID is case-sensitive. To ingest all metadata from a Tableau site in the specified domain, specify the site name and a separate domain ID for each site that you list on the siteIds property in the lineage harvester configuration file for Tableau. If the site_name or domain_id property is not specified for a site, the metadata from the site is ingested in the default domain. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold. Show me the example { "filters":{ "sites":{ "Training":"ca60b822-781b-4b3a-b44d-f65bd107ff92" }, "projects":{ "Testing > Databricks":"e8f4e4a8-4062-4a33-9b44-3ce3e18e4e22", "Product Demo > Customer Insights":"a305e6f7-7a49-49aa-aa85-41b1e689121b" } } } projects The Tableau projects to be ingested and the domain in which you want to ingest metadata from the Tableau projects or sub-projects. Tip Project filtering is not relevant for those who have an Explorer role in Tableau, because Explorers need to configure permissions for each data object in Tableau that they want to ingest. As the Administrator role has access to all data objects, project filtering allows Administrators to specify which projects to ingest. site_name > project_name : domain_id The site_name should be the Tableau site name. The project_name should be the Tableau project name. The domain_id should be the unique reference ID of the domain in Collibra in which you want to ingest metadata. When you specify the site and project names, the following rules apply: Add spaces before and after >. The spaces are separators between the site and project. Specify the full exact site and project names. The values are case-sensitive. When you specify a Tableau project, all assets in the project are ingested in the specified domain. If you want to ingest assets from different Tableau projects in one domain, you can specify the same value for domain id for different projects. Example "Collibra_tab_partner_site > JB_Test_2812": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" site_name > project_name > sub-project_name : domain_id The site_name should be the Tableau site name. The project_name should be the Tableau project name. Optionally, use sub-project_name to specify the Tableau sub-project name. The domain_id property should be the unique reference ID of the domain in Collibra in which you want to ingest metadata. When you specify the site, project and sub-project names, the following rules apply: Add spaces before and after >. The spaces are separators between the site and project. Specify the full exact site and project names. The values are case-sensitive. Example "Collibra_tab_partner_site > JB_Test_2812 > ProjectJJ2": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" domainMapping This section defines in which domains in Collibra you want to ingest assets from your Tableau sites and Tableau projects. Domain mapping is transitive, meaning that all resources, such as Tableau workbooks and data attributes in a parent Tableau site, project or sub-project, are ingested in the same domain as the parent. Important The domainMapping and filters sections are mutually exclusive. Do not include both domainMapping and filters sections in your JSON file. Tip  If you want to ingest all of the projects in a Tableau site into multiple domains in Collibra, use this domainMapping section. If you want to ingest all of the projects in a Tableau site into the default domain, use only the domainID property in the lineage harvester configuration file. The domainID property represents the default domain. Note Tableau assets that are not mapped to specific domains via this domainMapping section, for example Tableau Server assets, are ingested in that default domain. If you want to ingest all of the projects in a Tableau site into a single domain in Collibra, use site filtering. If you want to ingest metadata from only some of the projects in a Tableau site, use project filtering. Show me an example Let's say that you have a Tableau site named "Site-1". You want to ingest all Tableau projects in "Site-1" in a domain named "Domain-1" in Collibra, with the exception of one Tableau project named "Project-Default", which you want to ingest in "Domain-2". You should configure the domainMapping section as follows. "domainMapping": { "<Site-1>": "reference-id-of-Domain-1", "<Site-1> > <Project-Default>": "reference-id-of-Domain-2" } If you want to specify a domain for a sub-project of "Project-Default", use the <site name> > <project name> > <sub-project name> property, as described below. Tip For the properties in this domainMapping section, ensure that you maintain the spaces before and after ">", for example "Site-1 > Project-Default". The spaces serve as a separator between the site and the projects. site name The Tableau site name, followed by the unique reference ID of the domain in Collibra in which you want to ingest resources from the Tableau site. Important In the configuration file, use the actual site name, along with the domain reference ID, for example: "Collibra_tab_partner_site": "afc8cfb0-91f1-4075-a3e5-7ce6d1f9bcc9" site name > project name The Tableau project name, preceded by the name of the Tableau site to which it belongs, and followed by the unique reference ID of the domain in Collibra in which you want to ingest resources from the Tableau project. Important In the configuration file, use the actual site and project names, along with the domain reference ID, for example: "Collibra_tab_partner_site > JB_Test_2812": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" site name > project name > sub-project name The Tableau sub-project name, preceded by the name of the Tableau site and project to which it belongs, and followed by the unique reference ID of the domain in Collibra in which you want to ingest resources from the Tableau sub-project. Important In the configuration file, use the actual site, project and sub-project names, along with the domain reference ID, for example: "Collibra_tab_partner_site > JB_Test_2812 > ProjectJJ2": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" Example  See an example <source ID> configuration file for database mapping and filtering. For more hostnameMapping configuration examples and results, go to Tableau hostname, schema, and system name mapping. { "collibraSystemNames": { "files": [ {"filePath": "C:\\ProgramData\\Tableau\\Tableau Server\\data\\files\\sample.xls", "collibraSystemName": "sample-files" } ], "connectors": [ { "connectorUrl": "tableau-server-connector-url.com", "collibraSystemName": "Oracle-connector" } ], "cloudFiles": [ { "name": "file-name", "collibraSystemName": "FILE" } ] }, "hostnameMapping": { "found_dbname=*;found_hostname=abc.net;found_schema=DEFAULT": { "dbname": "CData", "schema": "Jan_1_2022", "dialect": "spark", "collibraSystemName": "TV_testing" } }, "filters": { "sites":{ "site_name":"domain_id" }, "projects":{ "site_name2 > project_name2": "domain-reference-id2", "site_name3 > project_name3 > subproject_name": "domain-reference-id2" } } } Tip Click to copy the example to your clipboard. See an example <source ID> configuration file for host name mapping and domain mapping. For more hostnameMapping configuration examples and results, go to Tableau hostname, schema, and system name mapping. { "collibraSystemNames": { "files": [ {"filePath": "C:\\ProgramData\\Tableau\\Tableau Server\\data\\files\\sample.xls", "collibraSystemName": "sample-files" } ], "connectors": [ { "connectorUrl": "tableau-server-connector-url.com", "collibraSystemName": "Oracle-connector" } ], "cloudFiles": [ { "name": "file-name", "collibraSystemName": "FILE" } ] }, "hostnameMapping": { "found_dbname=Test;found_hostname=*;found_schema=DEFAULT": { "dbname": "CData", "schema": "Jan_1_2022", "dialect": "spark", "collibraSystemName": "TV_testing" } }, "domainMapping": { "<Site-1>": "reference-id-of-Domain-1", "<Site-1> > <Project-Default>": "reference-id-of-Domain-2" } } Tip Click to copy the example to your clipboard.	No
       Custom Properties	This section identifies to which Collibra Data Lineage service instance you want to upload the Tableau metadata. Warning This applies only for Collibra Cloud for Government customers.
       techlinKey	The unique API key to connect to the Collibra Data Lineage service instance. A unique user key is needed for each Collibra environment. If you're not sure what your user key is, please contact your Collibra Customer Success Manager. Warning This applies only for Collibra Cloud for Government customers.	No
       techlinHost	The URL of he Collibra Data Lineage service instance to which you want to upload Tableau metadata, for example "techlin-gcp-eu.collibra.com". Warning This applies only for Collibra Cloud for Government customers.	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	No
       Paging	This section allows you to customize the Tableau API pagination settings. The default values are sufficient in most cases; however, you can decrease them to help mitigate node limit errors, or increase them to speed up API calls. The complete list of pagination settings, descriptions and default values "paging": { "databasesPageSize": 100, "tablesPageSize": 100, "tablesColumnsPageSize": 100, "tableColumnsPageSize": 1000, "datasourcesPageSize": 50, "datasourcesFieldsPageSize": 50, "datasourceFieldsPageSize": 100, "worksheetsPageSize": 100, "worksheetsFieldsPageSize": 100, "worksheetFieldsPageSize": 1000, "usersPageSize": 100, "dashboardsPageSize": 100, "columnsLimit": 20, "fieldsLimit": 20 } Settings per metadata type and descriptions Metadata type Setting and description Dashboard dashboardsPageSize: The number of dashboards per page. Worksheet worksheetsPageSize: The number of worksheets per page. worksheetsFieldsPageSize: The number of worksheet fields per page. Database databasesPageSize: The number of databases per page. Table tablesPageSize: The number of tables per page. tablesColumnsPageSize: The number of table columns per page. Table columns tableColumnsPageSize: The number of table columns per page. Users usersPageSize: The number of users per page. Data source datasourcesPageSize: The number of data sources per page. datasourcesFieldsPageSize: The number of data source fields per page. columnsLimit: The number of data source field columns per page. fieldsLimit : The number of referenced data source fields per page. Data source field datasourceFieldsPageSize: The number of data source fields per page. columnsLimit: The number of data source field columns per page. fieldsLimit : The number of referenced data source fields per page.	No

       Field	Description	Required
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	No
       Source ID	The name of the data source. You can give this any name, as long as it is unique. Warning If you are switching between the lineage harvester and Edge, the value in this field must exactly match the value of the id property in your lineage harvester configuration file. Warning You can only specify one source ID per Tableau server or Tableau online account. If you have multiple unique source IDs that refer to a single Tableau server or Tableau online account, ingestion will fail. Put another way, if you have multiple unique source IDs, each must refer to a unique Tableau server or Tableau online account.	Yes
       Tableau connection	The Tableau connection that you created for ingestion in Data Catalog. Tip Select the name that you provided in the Name field when you created a connection to Tableau.	Yes
       Domain ID	The unique reference ID of the domain in Collibra Data Intelligence Platform in which you want to ingest the Tableau assets. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold.	Yes
       REST only	Indication whether or not you want to use both the Tableau REST API and Tableau Metadata API to harvest Tableau metadata. Cleared (default): The lineage harvester will use the REST API and Metadata API to harvest Tableau metadata. Selected: The lineage harvester will only use the REST API to harvest Tableau metadata. Note This filed must be cleared, to: Enable technical lineage and the automatic stitching of Column assets to Tableau Data Attribute assets. Harvest owner information for Tableau projects, workbooks and data models.	No
       Exclude images	Indication whether or not you want to excluding the downloading of images. Cleared: Images are downloaded. Selected (default): Images are not downloaded. Note The maximum number of images that can be uploaded to Collibra per day is determined by the configuration of the file upload service, in Collibra Console. For complete details, see the Upload configuration settings in DGC service configuration: options.	No
       Site ID	The site IDs of the Tableau sites that you want to include in the ingestion process. If you leave this field empty, Collibra Data Lineage will ingest the default Tableau site. To ingest from multiple Tableau sites, enter each site ID in a separate Site ID field. To ingest the default Tableau site, enter "Default" or leave the field empty. This field is not case sensitive. Warning If you enter "Default", you must include the double quotation marks. The site IDs of any other Tableau sites must not be enclosed in double quotation marks. If the formatting of the site IDs does not conform to this detail, ingestion will fail. See an example Let's say that you want to ingest from the default Tableau site and a site named "ABC". In the Site ID field, enter "Default" for the default Tableau site. Click Add property. An empty Site ID field is aded. In the new Site ID field, enter the ID of the Tableau site ABC. Tip Ensure that you specify the correct value. The correct value is the URL of the site to which you want to sign in. When you manually sign in to Tableau Server or Tableau Online, the site ID is the value that appears after /site/ in the browser address bar. In the following example URLs, the site ID is MarketingTeam: Tableau Server: http://MyServer/#/site/MarketingTeam/projects Tableau Online: https://10ay.online.tableau.com/#/site/MarketingTeam/workbooks On Tableau Server, however, the URL of the default site does not specify the site. For example, the URL for a view named Profits, on a site named Sales, is http://localhost/#/site/sales/views/profits. The URL for this same view on the default site is http://localhost/#/views/profits. The site name Sales does not figure in the URL.	No
       Site Name	The site name, or names, of the Tableau sites you specified in the Site ID field. If you don't provide a site ID in the Site ID field, in which case the default Tableau site is ingested, leave this field blank.	No
       Concurrency level	This field is intended to help if you are experiencing HTTP 401 Unauthorized errors due to too many concurrent HTTP calls, using the same token. It allows you to specify the internal sizing, meaning the amount of tasks that can be executed at the same time. The default value is "10", meaning as many as 10 HTTP requests can take place in parallel. Consider reducing the value if you are experiencing HTTP 401 Unauthorized errors. Setting the value to "1" effectively disables the concurrency level, so that HTTP requests will be run in a synchronous manner, instead of in parallel.	No
       Source configuration	This field allows you to provide JSON code for database mapping, domain mapping and filtering. If you previously integrated Tableau via the lineage harvester, you can copy and paste in this field the JSON code from your Tableau <source ID> configuration file. Connection definition properties Property Description collibraSystemNames This section contains the system information for different Tableau data sources. Depending on the kind of data source or connection, you have to specify how to connect to this data source. Tip For more information, see the Tableau documentation. We also recommend to check the list of supported connectors in Tableau. files This section contains connection information to one or more files in Tableau. Tip If you do not have files in Tableau, you can remove this section. filePath The full path to the file. For example, the path to a JSON file. collibraSystemName The system name of the file. connectors This section contains connection information to one or more connectors in Tableau. Tip  If you do not have connectors in Tableau, you can remove this section. The values that you specify for this property are not case-sensitive. connectorUrl The URL of the connector. For example, the URL to Google Analytics. collibraSystemName The system name of the connector. cloudFiles This section contains connection information to one or more cloud files in Tableau's input data. Tip If you do not have cloud files in Tableau, you can remove this section. name The name of the file. For example, the name of a Zendesk file. collibraSystemName The system name of the cloud file. hostnameMapping This section allows you to map Tableau technical database, server and schema names to the respective real names, to preserve stitching. Warning  hostnameMapping replaces the following deprecated properties, which have been removed from this topic: The databaseMapping property. The databases sub-section of the collibraSystemNames section. hostnameMapping must not be used in combination with either of these properties. If you use the hostnameMapping section, you can still use the collibraSystemName property in conjunction with the files, connectors or cloudfiles sub-sections. Example configuration "hostnameMapping": { "found_dbname=databasename1;found_hostname=*;found_schema=test": { "dbname": "mssql-database-name", "schema": "mssql-schema-name", "dialect": "mssql", "collibraSystemName": "mssql-system-name" } } found_dbname=<database name>;found_hostname=<server name>;found_schema=<schema name> The database information of supported data sources in Tableau that is typically collected by the lineage harvester. It allows you to specify the name of the database (found_dbname), on which server a database is running (found_hostname), and optionally, the name of the schema (found_schema). dbname The name of the database of a supported data source in Tableau. schema The name of the default schema of a supported data source in Tableau. If the lineage harvester fails to find a specific schema, it uses the default schema. dialect The dialect of the supported data source in Tableau. You don't have to specify a dialect; it will automatically be detected. If, however, you are using a dialect that is not supported, you can use this property to specify a supported dialect that is a close comparison. That way, most of your queries will be detected and processed. Show me a list of dialects of supported data sources in Tableau. redshift, for an Amazon Redshift data source. azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. greenplum, for a Greenplum data source. hive, for a HiveQL data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. hana, for a SAP HANA data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source. filters This section defines: From which Tableau sites and projects you want to harvest metadata. Into which domains in Collibra you want to ingest the corresponding assets. Filtering is transitive, which means that all resources in a specified project, such as Tableau workbooks and all sub-projects, are ingested. Tableau assets that are not mapped to the specified domains, for example the Tableau Server assets and the parent projects (if you specify their sub-projects), are ingested in the default domain. Important  Filtering does not affect the amount of raw metadata that is harvested from Tableau and sent to the Collibra Data Lineage service instance. Rather, it determines which metadata is ingested as assets in Data Catalog. The domainMapping and filters sections are mutually exclusive. Do not include both domainMapping and filters sections in your JSON file. Tip  If you want to ingest all of the projects in a Tableau site into multiple domains in Collibra, use the domainMapping section. If you want to ingest all of the projects in a Tableau site into the default domain, use only the domainID property in the lineage harvester configuration file. The domainID property represents the default domain. If you want to ingest all of the projects in a Tableau site into a single domain in Collibra, use site filtering. If you want to ingest metadata from only some of the projects in a Tableau site, use project filtering. You can use site filtering and project filtering together: If filtering on the same site, this "filtering" is actually domain mapping, because nothing is filtered out. The contents of the projects are ingested in the specified domains, and the rest of the contents of the site are ingested in a different, specified domain. If you are site filtering on a specific site and project filtering a different site, then site filtering is again a form of domain mapping, and the filtered projects are ingested in their specified domains. If your lineage harvester configuration file includes sites that are not mentioned in the filters section of your <source ID> configuration file, those sites are ingested in the default domain. sites The Tableau sites to be ingested and the domain in which you want to ingest metadata from the Tableau sites. Tip If you have only one Tableau site, do not include a sites section in your <source ID> file. Instead, use a projects section, to filter on Tableau projects. Include a sites section only if all of the following are true: You have more than one Tableau site. You want to ingest all of the metadata from only one Tableau site into a single domain in Collibra. The domain into which you want to ingest is not the default domain, meaning the domain specified in the domainId property in your lineage harvester configuration file. site_name: domain_id site_name The name of the site to be ingested. The site name is case-sensitive. domain_id The unique reference ID of the domain in Collibra in which you want to ingest metadata. The domain ID is case-sensitive. To ingest all metadata from a Tableau site in the specified domain, specify the site name and a separate domain ID for each site that you list on the siteIds property in the lineage harvester configuration file for Tableau. If the site_name or domain_id property is not specified for a site, the metadata from the site is ingested in the default domain. How do I find a domain reference ID? Open the relevant domain in Collibra. The URL looks like: https://<yourcollibrainstance>/domain/22258f64-40b6-4b16-9c08-c95f8ec0da26?view=00000000-0000-0000-0000-000000040001. In this example, the reference ID is in bold. Show me the example { "filters":{ "sites":{ "Training":"ca60b822-781b-4b3a-b44d-f65bd107ff92" }, "projects":{ "Testing > Databricks":"e8f4e4a8-4062-4a33-9b44-3ce3e18e4e22", "Product Demo > Customer Insights":"a305e6f7-7a49-49aa-aa85-41b1e689121b" } } } projects The Tableau projects to be ingested and the domain in which you want to ingest metadata from the Tableau projects or sub-projects. Tip Project filtering is not relevant for those who have an Explorer role in Tableau, because Explorers need to configure permissions for each data object in Tableau that they want to ingest. As the Administrator role has access to all data objects, project filtering allows Administrators to specify which projects to ingest. site_name > project_name : domain_id The site_name should be the Tableau site name. The project_name should be the Tableau project name. The domain_id should be the unique reference ID of the domain in Collibra in which you want to ingest metadata. When you specify the site and project names, the following rules apply: Add spaces before and after >. The spaces are separators between the site and project. Specify the full exact site and project names. The values are case-sensitive. When you specify a Tableau project, all assets in the project are ingested in the specified domain. If you want to ingest assets from different Tableau projects in one domain, you can specify the same value for domain id for different projects. Example "Collibra_tab_partner_site > JB_Test_2812": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" site_name > project_name > sub-project_name : domain_id The site_name should be the Tableau site name. The project_name should be the Tableau project name. Optionally, use sub-project_name to specify the Tableau sub-project name. The domain_id property should be the unique reference ID of the domain in Collibra in which you want to ingest metadata. When you specify the site, project and sub-project names, the following rules apply: Add spaces before and after >. The spaces are separators between the site and project. Specify the full exact site and project names. The values are case-sensitive. Example "Collibra_tab_partner_site > JB_Test_2812 > ProjectJJ2": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" domainMapping This section defines in which domains in Collibra you want to ingest assets from your Tableau sites and Tableau projects. Domain mapping is transitive, meaning that all resources, such as Tableau workbooks and data attributes in a parent Tableau site, project or sub-project, are ingested in the same domain as the parent. Important The domainMapping and filters sections are mutually exclusive. Do not include both domainMapping and filters sections in your JSON file. Tip  If you want to ingest all of the projects in a Tableau site into multiple domains in Collibra, use this domainMapping section. If you want to ingest all of the projects in a Tableau site into the default domain, use only the domainID property in the lineage harvester configuration file. The domainID property represents the default domain. Note Tableau assets that are not mapped to specific domains via this domainMapping section, for example Tableau Server assets, are ingested in that default domain. If you want to ingest all of the projects in a Tableau site into a single domain in Collibra, use site filtering. If you want to ingest metadata from only some of the projects in a Tableau site, use project filtering. Show me an example Let's say that you have a Tableau site named "Site-1". You want to ingest all Tableau projects in "Site-1" in a domain named "Domain-1" in Collibra, with the exception of one Tableau project named "Project-Default", which you want to ingest in "Domain-2". You should configure the domainMapping section as follows. "domainMapping": { "<Site-1>": "reference-id-of-Domain-1", "<Site-1> > <Project-Default>": "reference-id-of-Domain-2" } If you want to specify a domain for a sub-project of "Project-Default", use the <site name> > <project name> > <sub-project name> property, as described below. Tip For the properties in this domainMapping section, ensure that you maintain the spaces before and after ">", for example "Site-1 > Project-Default". The spaces serve as a separator between the site and the projects. site name The Tableau site name, followed by the unique reference ID of the domain in Collibra in which you want to ingest resources from the Tableau site. Important In the configuration file, use the actual site name, along with the domain reference ID, for example: "Collibra_tab_partner_site": "afc8cfb0-91f1-4075-a3e5-7ce6d1f9bcc9" site name > project name The Tableau project name, preceded by the name of the Tableau site to which it belongs, and followed by the unique reference ID of the domain in Collibra in which you want to ingest resources from the Tableau project. Important In the configuration file, use the actual site and project names, along with the domain reference ID, for example: "Collibra_tab_partner_site > JB_Test_2812": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" site name > project name > sub-project name The Tableau sub-project name, preceded by the name of the Tableau site and project to which it belongs, and followed by the unique reference ID of the domain in Collibra in which you want to ingest resources from the Tableau sub-project. Important In the configuration file, use the actual site, project and sub-project names, along with the domain reference ID, for example: "Collibra_tab_partner_site > JB_Test_2812 > ProjectJJ2": "d224a1a5-43b4-43b2-8df0-ddf8f2726b82" Example  See an example <source ID> configuration file for database mapping and filtering. For more hostnameMapping configuration examples and results, go to Tableau hostname, schema, and system name mapping. { "collibraSystemNames": { "files": [ {"filePath": "C:\\ProgramData\\Tableau\\Tableau Server\\data\\files\\sample.xls", "collibraSystemName": "sample-files" } ], "connectors": [ { "connectorUrl": "tableau-server-connector-url.com", "collibraSystemName": "Oracle-connector" } ], "cloudFiles": [ { "name": "file-name", "collibraSystemName": "FILE" } ] }, "hostnameMapping": { "found_dbname=*;found_hostname=abc.net;found_schema=DEFAULT": { "dbname": "CData", "schema": "Jan_1_2022", "dialect": "spark", "collibraSystemName": "TV_testing" } }, "filters": { "sites":{ "site_name":"domain_id" }, "projects":{ "site_name2 > project_name2": "domain-reference-id2", "site_name3 > project_name3 > subproject_name": "domain-reference-id2" } } } Tip Click to copy the example to your clipboard. See an example <source ID> configuration file for host name mapping and domain mapping. For more hostnameMapping configuration examples and results, go to Tableau hostname, schema, and system name mapping. { "collibraSystemNames": { "files": [ {"filePath": "C:\\ProgramData\\Tableau\\Tableau Server\\data\\files\\sample.xls", "collibraSystemName": "sample-files" } ], "connectors": [ { "connectorUrl": "tableau-server-connector-url.com", "collibraSystemName": "Oracle-connector" } ], "cloudFiles": [ { "name": "file-name", "collibraSystemName": "FILE" } ] }, "hostnameMapping": { "found_dbname=Test;found_hostname=*;found_schema=DEFAULT": { "dbname": "CData", "schema": "Jan_1_2022", "dialect": "spark", "collibraSystemName": "TV_testing" } }, "domainMapping": { "<Site-1>": "reference-id-of-Domain-1", "<Site-1> > <Project-Default>": "reference-id-of-Domain-2" } } Tip Click to copy the example to your clipboard.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	No
       Paging	This section allows you to customize the Tableau API pagination settings. The default values are sufficient in most cases; however, you can decrease them to help mitigate node limit errors, or increase them to speed up API calls. The complete list of pagination settings, descriptions and default values "paging": { "databasesPageSize": 100, "tablesPageSize": 100, "tablesColumnsPageSize": 100, "tableColumnsPageSize": 1000, "datasourcesPageSize": 50, "datasourcesFieldsPageSize": 50, "datasourceFieldsPageSize": 100, "worksheetsPageSize": 100, "worksheetsFieldsPageSize": 100, "worksheetFieldsPageSize": 1000, "usersPageSize": 100, "dashboardsPageSize": 100, "columnsLimit": 20, "fieldsLimit": 20 } Settings per metadata type and descriptions Metadata type Setting and description Dashboard dashboardsPageSize: The number of dashboards per page. Worksheet worksheetsPageSize: The number of worksheets per page. worksheetsFieldsPageSize: The number of worksheet fields per page. Database databasesPageSize: The number of databases per page. Table tablesPageSize: The number of tables per page. tablesColumnsPageSize: The number of table columns per page. Table columns tableColumnsPageSize: The number of table columns per page. Users usersPageSize: The number of users per page. Data source datasourcesPageSize: The number of data sources per page. datasourcesFieldsPageSize: The number of data source fields per page. columnsLimit: The number of data source field columns per page. fieldsLimit : The number of referenced data source fields per page. Data source field datasourceFieldsPageSize: The number of data source fields per page. columnsLimit: The number of data source field columns per page. fieldsLimit : The number of referenced data source fields per page.	No
       Debug	This setting is not valid for this integration. It should be set to false.	No
       Log level	This setting is not valid for this integration. It should be set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for Teradata	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       External Database Name	The database value to be used as the database name in the full path (system -> database -> schema -> table). Use this field to ensure successful stitching for a database-less data source. You can specify one of the following values: CData, which Cdata drivers returned as a placeholder. Use this value if you did not create a custom database name by using the CustomizedDefaultCatalogName property when you registered your data source. The custom database name that you specified for the CustomizedDefaultCatalogName property when you registered your data source. See an example When you registered a Teradata data source on Edge and did not specify the CustomizedDefaultCatalogName property, the following full path to a column in Data Catalog is created and CData is used as the database name:  Teredata_123 (system) > CData (database) > Teredata_ABC (schema) > Table > Column When Collibra Data Lineage collects metadata from the Teradata data source, the value of the Database Name field is used as the schema name because Teradata is database-less. If you do not enter a value for the External Database Name field, the value of the Collibra System Name field is used as the database name. If you set the Collibra system name setting to true, the value of the Collibra System Name field is also used as the system name. In this case, the full path is shown as follows and does not match the full path in Data Catalog: Teredata_123 (system) > Teredata_123 (database) > Teredata_ABC (schema) > Table > Column In this case, the stitching fails because of the mismatch of the full paths. To match the full path and preserve stitching, you must specify CData for the External Database Name field.	No
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Object Names This query retrieves a list of object names from which technical lineage can be created. The objects can include stored procedures, views, macros, and so on.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Logging	This section contains general information about logging.
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       JDBC Connection	The JDBC connection that you created for Catalog JDBC ingestion.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       External Database Name	The database value to be used as the database name in the full path (system -> database -> schema -> table). Use this field to ensure successful stitching for a database-less data source. You can specify one of the following values: CData, which Cdata drivers returned as a placeholder. Use this value if you did not create a custom database name by using the CustomizedDefaultCatalogName property when you registered your data source. The custom database name that you specified for the CustomizedDefaultCatalogName property when you registered your data source. See an example When you registered a Teradata data source on Edge and did not specify the CustomizedDefaultCatalogName property, the following full path to a column in Data Catalog is created and CData is used as the database name:  Teredata_123 (system) > CData (database) > Teredata_ABC (schema) > Table > Column When CollibraData Lineage collects metadata from the Teradata data source, the value of the Database Name field is used as the schema name because Teradata is database-less. If you do not enter a value for the External Database Name field, the value of the Collibra System Name field is used as the database name. If you set the Collibra system name setting to true, the value of the Collibra System Name field is also used as the system name. In this case, the full path is shown as follows and does not match the full path in Data Catalog: Teredata_123 (system) > Teredata_123 (database) > Teredata_ABC (schema) > Table > Column In this case, the stitching fails because of the mismatch of the full paths. To match the full path and preserve stitching, you must specify CData for the External Database Name field.	No
       Database Name	The name of your database, which is also the name of your Database asset in Data Catalog.	Yes
       Queries	The queries to download all the data that is required to create technical lineage. The queries vary depending on the data source you use. The query code is automatically available. However, you can modify the query code if needed. Example Enter the following filter in a Views query: where v.table_schema not in ('pg_catalog', 'information_schema');. This query excludes the pg_catalog and information_schema schemas, which don't contain customer data. If you want to exclude other schemas, adjust the query to, for example where v.table_schema not in ('pg_catalog', 'information_schema', 'another_schema');. Note  If you change queries, you can only use supported SQL syntax. Collibra Support does not provide support for customized SQL files. Query Description Columns This query retrieves the columns, tables, schemas, databases or projects fields in the form: database or project > schema > table > column. Object Names This query retrieves a list of object names from which technical lineage can be created. The objects can include stored procedures, views, macros, and so on.	Yes
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.	No
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes
       Debug	An option to enable logging of a JDBC job. If you enable logging, you can download the output file of the JDBC job in the Edge Jobs dashboard (beta). The output file contains the logs of the JDBC driver. For more information about downloading the output file, go to Download job output files. Select one of the following values: True Enables logging of the JDBC job. False Disables logging of the JDBC job. This is the default value.	No
       Log level	An option to determine the verbosity level of Catalog connector log files. By default, this option is set to No logging.	No

       Field	Description	Required?
       Capability	This section contains general information about the capability.
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Main Properties	This section contains the information for creating a technical lineage.
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Advanced Properties	This section contains the advanced properties for creating a technical lineage.
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

       Field	Description	Required?
       Name	The name of the Edge capability.	Yes
       Description	The description of the Edge capability.	Yes
       Capability template	The capability template. The value that you select in this field determines which sections appear on the page. Select the following Edge capability: Technical Lineage for SqlDirectory	Yes
       Source ID	The name of the data source. Specify a name that is unique.	Yes
       Shared Storage Connection	The Shared Storage connection that you created.	No
       Mask	The pattern of the file names in the directory. By default, the value is *.	Yes
       Dialect	The dialect of the database. See the list of allowed values. You can enter one of the following values: azure, for an Azure SQL Server data source. bigquery, for a Google BigQuery data source. db2, for an IBM DB2 data source. hana, for an SAP HANA data source. hana-cviews, for getting lineage from calculated views in an SAP HANA Classic on-premises data source. hana-cviews-v2, for getting lineage from calculated views in an SAP HANA Cloud/Advanced data source. Important  To get technical lineage including calculated views, you must harvest SAP HANA by adding two Technical Lineage for SqlDirectory capabilities with the Shared Storage connections. In one capability, specify the hana dialect, and in the other, specify the hana-cviews or hana-cviews-v2 dialect. hive, for a HiveQL data source. greenplum, for a Greenplum data source. mssql, for a Microsoft SQL Server data source. mysql, for a MySQL data source. netezza, for a Netezza data source. oracle, for an Oracle data source. postgres, for a PostgreSQL data source. redshift, for an Amazon Redshift data source. snowflake, for a Snowflake data source. spark, for a Spark SQL data source. sybase, for a Sybase data source. teradata, for a Teradata data source.	Yes
       Collibra System Name	The system or server name of the data source. This field is also the full name of your System asset in Data Catalog. The value of this field must be the same as the full name of the System asset that you created when you registered the data source.	Yes
       Database	The name of your database, which is also the name of your Database asset in Data Catalog. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Schema	The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset. Note The database and schema names in the SQL statements in your SQL files take precedence over the values that you provide for the Database and Schema fields in the technical lineage for SqlDirectory capability. If your SQL statements contain database and schema names, Collibra Data Lineage uses them for stitching. If your SQL statements do not contain database and schema names, Collibra Data Lineage uses the values of the Database and Schema fields in the capability for stitching. Fore more information, go to Prepare the SQL directory and Automatic stitching for technical lineage.	Yes
       Database-System mapping	This optional property allows you to map databases to their rightful systems, to obtain stitching. This resolves missing stitching, which occurs when Collibra Data Lineage associates multiple databases with the default system name that you provide in the collibraSystemName property. More information and example configuration Let’s say you use the collibraSystemName property to specify the system name SystemA. This system name will be associated with all of the databases mentioned in your SQL statements in your SQL files. Now let’s say that you have a SQL statement that selects data from a database DB2 (which is in SystemB) and inserts the data in database DB3 (which is part of SystemC). Both of these databases will be associated with SystemA, and both will appear under SystemA in the Browse tab pane. Therefore, stitching fails and duplicate databases might appear. To resolve this issue and obtain stitching, you can use this field to map DB2 to its rightful SystemB, and DB3 to its rightful SystemC.	No
       Property	This section contains the custom parameters you can specify to create technical lineage. Click Add property to add a property. Warning This applies only for Collibra Cloud for Government customers.   Possible properties for Collibra Cloud for Government customers Name Description Type Encryption Example value techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Text Not encrypted (plain text) https://techlin-gcp-dev.collibra.com techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. Text To be encrypted by Edge management server Value will be stored on Edge Type Value Type Name Value Text Plaintext techlinHost This is the URL of the Collibra Data Lineage service instance to which you want to upload metadata, for example techlin-gcp-eu.collibra.com. Example: https://techlin-gcp-dev.collibra.com Text Secret techlinKey This is the unique API key to connect to a Collibra Data Lineage service instance. Specify a unique user key for each Collibra environment. If you're not sure what your user key is, contact your Collibra Customer Success Manager. <your-techlin-key> See an example	No
       Dependent On Sources (Beta)	This option allows you to provide table-definition details from an independent data source to a data source that is dependent on those details. This is needed to avoid analysis errors and to have a complete lineage that includes lineage from the SQL statements from dependent data sources. To use this option, enter the source ID of the independent source. Show me an example Let's consider an example. Let's say that you want to create a technical lineage for two data sources: Database1 contains the DDL that specifies that the database has a table named "Table1", which has three columns: Col1, Col2, Col3, and Col4. Database2 contains an SQL statement: SELECT * from Database1.Schema1.Table1. The SQL statement in Database2 refers to the table in Database1. Therefore, to get lineage from the statement in Database2, the table definition from Database1 must be known. In this case, we say that Database2 is dependent on Database1. Database1 is considered the independent data source. To configure this option, specify the Source ID of the independent data source, in this example, Database1, as shown in the following imagee For complete information, go to Sharing database models across data sources.
       Delete Raw Metadata After Processing	Technical lineage via Edge harvests raw metadata from specified data sources and uploads it in a ZIP file to a Collibra Data Lineage service instance. This option indicates whether the raw metadata should be deleted from the Collibra Data Lineage service instance after the metadata that is targeted for ingestion in Data Catalog is processed. Select this option to indicate that the raw source metadata is deleted after processing. Clear the checkbox to keep the raw source metadata after processing. In this case, it is stored in the Collibra infrastructure. Note Selecting this option can negatively impact performance.	No
       Analyze Only	This option determines whether to only load and analyze the source data on the Collibra Data Lineage service instances. When you select this option, the technical lineage of the data source is not created during the synchronization of the capability. Selecting this option is equivalent to entering the load-sources and analyze command with a source specified when you use the lineage harvester. This option is not enabled by default. Use case You can use this option to control when to start full synchronization of data sources. For example if you have three data sources, A, B, and C, you can synchronize the data sources as follows: During weekdays, synchronize data sources A and B with the Analyze Only checkbox selected in the capabilities. Collibra Data Lineage only loads and analyzes data sources A and B without synchronizing the technical lineage. On the weekend, synchronize data source C without selecting the Analyze Only checkbox in the capability. Collibra Data Lineage synchronizes the technical lineage for all data sources including A, B, and C.	No
       Active	The option determines whether to include or remove the technical lineage of the data source. Select this option to include the technical lineage of this data source. Clear the checkbox to exclude the technical lineage of this data source.	Yes

    5. Click Save.
       The capability is added to the Edge site.
       The fields become read-only.
    6. Click Create.
       The capability is added to the Edge site.
       The fields become read-only.
Synchronize your technical lineage.

You can synchronize your technical lineage manually or automatically by adding a synchronization schedule.

If you want to synchronize technical lineage by using the Collibra Catalog Cloud Ingestions API, use the /genericIntegration/{ingestibleId}/run API, where {ingestibleId} is the capability ID.

If you synchronize a capability without selecting the Analyze Only option in the capability, a full synchronization is run, which is equivalent to the full-sync command with the -s argument specified when you use the lineage harvester. You can synchronize as many technical lineage capabilities in parallel as you want. If a full synchronization is in progress, the other capabilities are put in a queue until the existing synchronization completes. Then, this new synchronization starts automatically.

If you include multiple databases in your technical lineage capability template, you don't have to synchronize each database separately. One synchronization job will harvest the metadata from all relevant databases.

Note During the ingestion process, relations of the type "Data Element targets / sources Data Element" are automatically created between certain assets. Any relations of this type that you manually create between assets will be deleted during the synchronization process.

Prerequisites

• A global role that has the following global permission:
  • Catalog, for example Catalog Author
  • View Edge connections and capabilities
• A resource role with Configure external system resource permission, for example Owner.
• Data source-specific permissions.

Steps

• Manually synchronize the technical lineage
• Add a synchronization schedule

1. Open a Database asset page of a registered database.
2. In the tab panebar, click Configuration.
3. On the Lineage Extraction tab pane, click Synchronize Lineage.
   A notification indicates synchronization has started.
   The synchronization job is started. The lineage is ingested based on the configuration provided.

1. Open the Database asset page of a registered database.
2. In the tab panebar, click Configuration.
3. On the Lineage Extraction tab pane, click Add Schedule.
4. Enter the required information and click Save:

   Field	Description
   Repeat	The interval when you want to synchronize automatically. The possible values are: Daily, Weekly, Monthly, and Cron expression.
   Cron	The Quartz Cron expression that determines when the synchronization takes place. This field is only visible if you select Cron expression in the Repeat field.
   Every	The day on which you want to synchronize, for example, Sunday. This field is only visible if you select Weekly in the Repeat field.
   Every first	The day of the month on which you want to synchronize, for example, Tuesday. This field is only visible if you select Monthly in the Repeat field.
   At	The time at which you want to synchronize automatically, for example, 14:00. You can only schedule on the hour. For example, you can add a synchronization schedule at 8:00, but not at 8:45. If you try to add it at 8:45, we will default it to 8:00. Use a cron expression if you don't want to schedule on the hour. This field is only visible if you select Daily, Weekly, or Monthly in the Repeat field.
   Time zone	The time zone for the schedule.

Synchronize your technical lineage.

You can synchronize your technical lineage manually or automatically by adding a synchronization schedule.

If you want to synchronize technical lineage by using the Collibra Catalog Cloud Ingestions API, use the /genericIntegration/{ingestibleId}/run API, where {ingestibleId} is the capability ID.

If you synchronize a capability without selecting the Analyze Only option in the capability, a full synchronization is run, which is equivalent to the full-sync command with the -s argument specified when you use the lineage harvester. You can synchronize as many technical lineage capabilities in parallel as you want. If a full synchronization is in progress, the other capabilities are put in a queue until the existing synchronization completes. Then, this new synchronization starts automatically.

If you include multiple databases in your technical lineage capability template, you don't have to synchronize each database separately. One synchronization job will harvest the metadata from all relevant databases.

Note During the ingestion process, relations of the type "Data Element targets / sources Data Element" are automatically created between certain assets. Any relations of this type that you manually create between assets will be deleted during the synchronization process.

Prerequisites

• A global role that has the following global permission:
  • Catalog, for example Catalog Author
  • View Edge connections and capabilities
• A resource role with Configure external system resource permission, for example Owner.
• Data source-specific permissions.

• The permissions to retrieve the metadata of the following database components through the JDBC Driver Database Metadata methods:
  • Schemas
  • Tables
  • Columns

Steps

• Manually synchronize the technical lineage
• Add a synchronization schedule

1. On the main toolbar, click , and then click Catalog.
   The Catalog Home opens.
2. On the main toolbar, click .
   The Create dialog box appears.
3. In the Register with Edge section of the Create dialog box, click Register a data sourceIntegration Configuration.
   The Register contentIntegration Configuration tab page opens.
4. In the Connnection nameConnnection Name column, locate the connection that you used when you added the technical lineage capability. Then, click the capability name in the Data sources/CapabilitiesCapabilities column of your connection.
   
   The technical lineage capability configuration page opens.
5. On the Configuration SectionSynchronize Configuration tab pane, click Synchronize nowSynchronize.
   A notification indicates synchronization has started.
   The synchronization job is started. The lineage is ingested based on the configuration provided.

1. On the main toolbar, click , and then click Catalog.
   The Catalog Home opens.
2. On the main toolbar, click .
   The Create dialog box appears.
3. In the Register with Edge section of the Create dialog box, click Register a data sourceIntegration Configuration.
   The Register contentIntegration Configuration tab page opens.
4. In the Connnection nameConnnection Name column, locate the connection that you used when you added the technical lineage capability. Then, click the capability name in the Data sources/CapabilitiesCapabilities column of your connection.
   
   The technical lineage capability configuration page opens.
5. On the Synchronization scheduleSynchronization Schedule tab pane, click Add scheduleAdd schedule.
6. Enter the required information and click Save:

   Field	Description
   Repeat	The interval when you want to synchronize automatically. The possible values are: Daily, Weekly, Monthly, and Cron expression.
   Cron	The Quartz Cron expression that determines when the synchronization takes place. This field is only visible if you select Cron expression in the Repeat field.
   Every	The day on which you want to synchronize, for example, Sunday. This field is only visible if you select Weekly in the Repeat field.
   Every first	The day of the month on which you want to synchronize, for example, Tuesday. This field is only visible if you select Monthly in the Repeat field.
   At	The time at which you want to synchronize automatically, for example, 14:00. You can only schedule on the hour. For example, you can add a synchronization schedule at 8:00, but not at 8:45. If you try to add it at 8:45, we will default it to 8:00. Use a cron expression if you don't want to schedule on the hour. This field is only visible if you select Daily, Weekly, or Monthly in the Repeat field.
   Time zone	The time zone for the schedule.

Synchronize your technical lineage.

You can synchronize your technical lineage manually or automatically by adding a synchronization schedule.

If you want to synchronize technical lineage by using the Collibra Catalog Cloud Ingestions API, use the /genericIntegration/{ingestibleId}/run API, where {ingestibleId} is the capability ID.

If you synchronize a capability without selecting the Analyze Only option in the capability, a full synchronization is run, which is equivalent to the full-sync command with the -s argument specified when you use the lineage harvester. You can synchronize as many technical lineage capabilities in parallel as you want. If a full synchronization is in progress, the other capabilities are put in a queue until the existing synchronization completes. Then, this new synchronization starts automatically.

If you include multiple databases in your technical lineage capability template, you don't have to synchronize each database separately. One synchronization job will harvest the metadata from all relevant databases.

Note During the ingestion process, relations of the type "Data Element targets / sources Data Element" are automatically created between certain assets. Any relations of this type that you manually create between assets will be deleted during the synchronization process.

Prerequisites

• A global role that has the following global permission:
  • Catalog, for example Catalog Author
  • View Edge connections and capabilities
• A resource role with Configure external system resource permission, for example Owner.
• Data source-specific permissions.

• The permissions to retrieve the metadata of the following database components through the JDBC Driver Database Metadata methods:
  • Schemas
  • Tables
  • Columns

Steps

• Manually synchronize the technical lineage
• Add a synchronization schedule

1. On the main toolbar, click , and then click Catalog.
   The Catalog Home opens.
2. On the main toolbar, click .
   The Create dialog box appears.
3. In the Register with Edge section of the Create dialog box, click Register a data sourceIntegration Configuration.
   The Register contentIntegration Configuration tab page opens.
4. In the Connnection nameConnnection Name column, locate the connection that you used when you added the technical lineage capability. Then, click the capability name in the Data sources/CapabilitiesCapabilities column of your connection.
   
   The technical lineage capability configuration page opens.
5. On the Configuration SectionSynchronize Configuration tab pane, click Synchronize nowSynchronize.
   A notification indicates synchronization has started.
   The synchronization job is started. The lineage is ingested based on the configuration provided.

1. On the main toolbar, click , and then click Catalog.
   The Catalog Home opens.
2. On the main toolbar, click .
   The Create dialog box appears.
3. In the Register with Edge section of the Create dialog box, click Register a data sourceIntegration Configuration.
   The Register contentIntegration Configuration tab page opens.
4. In the Connnection nameConnnection Name column, locate the connection that you used when you added the technical lineage capability. Then, click the capability name in the Data sources/CapabilitiesCapabilities column of your connection.
   
   The technical lineage capability configuration page opens.
5. On the Synchronization scheduleSynchronization Schedule tab pane, click Add scheduleAdd schedule.
6. Enter the required information and click Save:

   Field	Description
   Repeat	The interval when you want to synchronize automatically. The possible values are: Daily, Weekly, Monthly, and Cron expression.
   Cron	The Quartz Cron expression that determines when the synchronization takes place. This field is only visible if you select Cron expression in the Repeat field.
   Every	The day on which you want to synchronize, for example, Sunday. This field is only visible if you select Weekly in the Repeat field.
   Every first	The day of the month on which you want to synchronize, for example, Tuesday. This field is only visible if you select Monthly in the Repeat field.
   At	The time at which you want to synchronize automatically, for example, 14:00. You can only schedule on the hour. For example, you can add a synchronization schedule at 8:00, but not at 8:45. If you try to add it at 8:45, we will default it to 8:00. Use a cron expression if you don't want to schedule on the hour. This field is only visible if you select Daily, Weekly, or Monthly in the Repeat field.
   Time zone	The time zone for the schedule.

Synchronize your technical lineage.

You can synchronize your technical lineage manually or automatically by adding a synchronization schedule.

If you want to synchronize technical lineage by using the Collibra Catalog Cloud Ingestions API, use the /genericIntegration/{ingestibleId}/run API, where {ingestibleId} is the capability ID.

If you synchronize a capability without selecting the Analyze Only option in the capability, a full synchronization is run, which is equivalent to the full-sync command with the -s argument specified when you use the lineage harvester. You can synchronize as many technical lineage capabilities in parallel as you want. If a full synchronization is in progress, the other capabilities are put in a queue until the existing synchronization completes. Then, this new synchronization starts automatically.

If you include multiple databases in your technical lineage capability template, you don't have to synchronize each database separately. One synchronization job will harvest the metadata from all relevant databases.

Note During the ingestion process, relations of the type "Data Element targets / sources Data Element" are automatically created between certain assets. Any relations of this type that you manually create between assets will be deleted during the synchronization process.

Steps

• Manually synchronize technical lineage
• Add a synchronization schedule

1. On the main toolbar, click , and then click Catalog.
   The Catalog Home opens.
2. On the main toolbar, click .
   The Create dialog box appears.
3. In the Register with Edge section of the Create dialog box, click Register a data sourceIntegration Configuration.
   The Register contentIntegration Configuration tab page opens.
4. In the Connection name column, locate the Databricks connection that you used when you added the technical lineage capability. Then, click the capability name in the Data sources/CapabilitiesCapabilities column of your Databricks connection.
   
   The technical lineage capability configuration page opens.
5. In the Configuration Section section, click Add Configuration.
6. Select the System asset in which the Databricks assets were ingested. Collibra Data Lineage stitches the ingested data objects to the selected assets when the synchronization of this capability starts.
7. In the Configuration Section section, click Synchronize now.
   A notification indicates synchronization has started.
   The synchronization job is started. CollibraData Lineage ingests the metadata from Databricks Unity Catalog and processes the metadata to create technical lineage.

1. On the main toolbar, click , and then click Catalog.
   The Catalog Home opens.
2. On the main toolbar, click .
   The Create dialog box appears.
3. In the Register with Edge section of the Create dialog box, click Register a data sourceIntegration Configuration.
   The Register contentIntegration Configuration tab page opens.
4. In the Connection name column, locate the Databricks connection that you used when you added the technical lineage capability. Then, click the capability name in the Data sources/CapabilitiesCapabilities column of your Databricks connection.
   
   The technical lineage capability configuration page opens.
5. In the Configuration Section section, click Add Configuration.
6. Select the System asset in which the Databricks assets were ingested. Collibra Data Lineage stitches the ingested data objects to the selected assets when the synchronization of this capability starts.
7. On the Synchronization scheduleSynchronization Schedule tab pane, click Add scheduleAdd Schedule.
8. Enter the required information and click Save:

   Field	Description
   Repeat	The interval when you want to synchronize automatically. The possible values are: Daily, Weekly, Monthly, and Cron expression.
   Cron	The Quartz Cron expression that determines when the synchronization takes place. This field is only visible if you select Cron expression in the Repeat field.
   Every	The day on which you want to synchronize, for example, Sunday. This field is only visible if you select Weekly in the Repeat field.
   Every first	The day of the month on which you want to synchronize, for example, Tuesday. This field is only visible if you select Monthly in the Repeat field.
   At	The time at which you want to synchronize automatically, for example, 14:00. You can only schedule on the hour. For example, you can add a synchronization schedule at 8:00, but not at 8:45. If you try to add it at 8:45, we will default it to 8:00. Use a cron expression if you don't want to schedule on the hour. This field is only visible if you select Daily, Weekly, or Monthly in the Repeat field.
   Time zone	The time zone for the schedule.

26. View the summary of the results.

    After you synchronize the technical lineage, you can view the ingestion report. This shows the impact of technical lineage synchronization on the assets in Collibra Data Intelligence Platform.

    Steps

    1. Open the Activities list.
    2. In the row containing the synchronization job, click Result.
       
       The Lineage harvester synchronization results dialog box appears.
       
    3. In the row containing the synchronization job, click Result.
       
       The synchronization report summary appears.
       

    Tip The Job ID is useful if you need to troubleshoot the synchronization job with Collibra Support.

27. View the summary of the results.

    After you synchronize the technical lineage, you can view the ingestion report. This shows the impact of technical lineage synchronization on the assets in Collibra Data Intelligence Platform.

    Steps

    1. Open the Activities list.

    2. In the row for your capability, click Result.
       

       The Synchronization Result dialog box opens.
       
    3. In the row containing the synchronization job, click Result.
       
       The Synchronization Result dialog box opens.
       

    Tip The Job ID is useful if you need to troubleshoot the synchronization job with Collibra Support.

    If there are errors in the synchronization result, go to Technical lineage via Edge troubleshooting for Databricks in Collibra Support Portal for more information.