dbt Core source configuration

Updated:

Note This topic is only relevant if you are creating technical lineage via Edge. If you are using the CLI lineage harvester (deprecated), you need to create a <source ID> configuration file. The CLI harvester will officially reach its End of Life on July 31, 2026.

The Source configuration field in the dbt Core technical lineage Edge capability allows you to reduce the amount of data objects to be processed and enhance the lineage harvester performance.

The value of the Source configuration field must be a valid block of JSON code, for example:

Copy 
{
    "collibraSystemNames":{
        "projects":[
        {"collibraSystemName":"SystemName"}
        ]
    },
    "materializedMapping":{
        "ELS_MATERIALIZE_MULTIPLE_EXTERNAL_TABLES":"VIEW"
    }
}

The following table describes the various properties you can use in your JSON code block.

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 Collibra system names.

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.

In the following code example, the project is stitched to the systemname1 System asset in Data Catalog. 

{
   "collibraSystemNames":{
	"projects":[
	    {"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