Add an Edge capability to an Edge site

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Redshift

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

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.

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Azure

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Azure

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Azure

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

The name of the default schema, if not specified in the data source itself. This corresponds to the name of your Schema asset.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for DataStage

The name of the data source. Specify a name that is unique.

The Shared Storage connection that you created.

The pattern of the file names in the directory. By default, the value is *.

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.

{
  "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"
    }
  }   
}

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Db2

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Bigquery

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The ID of the project.

Tip You can add extra project IDs by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Greenplum

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Hive

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The database value to be used in the asset path (system -> database -> schema -> table).

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical lineage for Informatica Intelligent Cloud Services (IICS)

The name of the data source. Specify a name that is unique.

The Informatica Intelligent Cloud Services (IICS) connection that you created.

Note Collibra Data Intelligence Cloud 2023.03 or newer is required to use the Informatica Intelligent Cloud Services (IICS) connection.

The objects that you want to export. Each object requires a path and a type, for example:

"objects": [
	{
		"path" : "Sales",
		"type" : "Project"
	}, 
	{
		"path" : "Finance/Task_Flows",
		"type" : "Folder"
	},
	{
		"path" : "Common/Task_Flows/tf_CalendarDimension",
		"type" : "Taskflow"
	}
]

Tip For more information about the objects that you can export and the required information, go to the Informatica documentation.

The Informatica Intelligent Cloud Services parameter files.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Informatica PowerCenter

The name of the data source. Specify a name that is unique.

The Shared Storage connection that you created.

The pattern of the file names in the directory. By default, the value is *.

The connection definitions and system names. Specify the following properties in JSON format and enter the content in this field.

{
	"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"
			}
		]
	}
}	

{
	"DWH_EXPORT":

		{ "dbname": "DWH", "schema": "DBO" }
}

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Mysql

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Netezza

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Oracle

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Postgres

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Hana

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to determine whether to include or remove the technical lineage of the data source with the calculated views 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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Snowflake

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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.

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');.

If you select the SQL Snowflake ingestion mode, the following queries apply:

If you select the SQL-API Snowflake ingestion mode, the following queries apply:

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Mssql

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for SQL Server Integration Services (SSIS)

The name of the data source. Specify a name that is unique.

The Shared Storage connection that you created.

The pattern of the file names in the directory. By default, the value is *.

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.

{
  "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" : ""
    }

  }
}

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Sybase

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Teradata

The name of the data source. Specify a name that is unique.

The JDBC connection that you created for Catalog JDBC ingestion.

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.

The database value to be used in the asset path (system -> database -> schema -> table).

The name of your database.

Tip You can add extra database names by clicking Add property.

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');.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.

The name of the Edge capability.

The description of the Edge capability.

The capability template, which determines the next available sections.

Select the following Edge capability:

Technical Lineage for Custom Lineage

The name of the data source. Specify a name that is unique.

The Shared Storage connection that you created.

This section contains the advanced properties for creating a technical lineage.

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.

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.

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.

An option to automatically send Edge infrastructure log files to Collibra Data Intelligence Cloud. By default, this option is set to false.