Jonathan Javier PÉREZ
03/14/2024, 12:36 PMMR_XXXX_ ) prefix, so N developers can work in the same model at the same time without breaking other team member's code and/or model structure. Problem?:
Each time I run artifacts model (_-m elementary.edr.dbt_artifacts_) inside one stale MR I have to run the edr report refresh and artifacts, it's like it's retrieving all the model duration/tests from all MR_XXX datasets and assigning the the stale branch MR code to it. In other words, let's say:
• I have MR_1_a dataset where I run/test N models
â—¦ I have model a inside => uat_proj.MR__1__a.a
• I have MR_2_a dataset where I run/test N models
▪︎ uat_proj.MR_2_a.a
• I have the stale branch where I run my artifacts & edr report // So no specific dataset is created
The result is that in my final HTML report I only see test and model duration of uat_proj.MR_3_a.a - Which doesn't exists, so it's taking the metrics of one of the previous models. Have you encountered a similar use-case I can check?
Elementary version: 0.14.1
DBT bigquery version: 1.6.0
PROJECT LEVEL => disable_dbt_artifacts_autoupload: true
NOTE: There's only one elementary dataset inside our UAT environment, because we don't want to generate N elementary dataset/reports, we want a unified one.
Thanks in advance for the helpJonathan Javier PÉREZ
03/14/2024, 12:43 PMdisable_dbt_artifacts_autoupload
But may create some instabilityJonathan Javier PÉREZ
03/14/2024, 1:09 PM