Info |
---|
DBT Core is the self managed version of DBT. Artifacts that generated by DBT core need to be updated to include their project ID name and then pushed to the K landing directory. |
...
The following are the naming conventions for these dbt artefacts.
The project id name can be found in the manifestdbt_project.json yaml file.
<project_id>name>_manifest.json | generated by |
<project_id>name>_catalog.json | generated by |
<project_id>name>_run_results_YYYYMMDDHHmmss.json | generated from Optional but required for usage information in KADA. |
mapping.json | manually created for your environment. |
...
A mapping file is required to map dbt projects to KADA sources. Example
Code Block |
---|
{ "60125raw": "af33141.australia-east.azure", "76e1e02270ddad585ed8ebf607230deeb779b3e5transformed": "af33141.australia-east.azure" } |
The file is a json payload containing key, value pairs:
key - dbt project idname.
value - host of the database matching the KADA onboarded source’s host.
This can be found in Platform Admin > Sources > Edit source > See host name.
You can find the project id name in the manifest dbt_project.yaml file like below
...
Note |
---|
Update the mapping file when you create a new project in dbt. |
...