Hi <!channel>, A large, warm welcome to all our new members! hello It would help us so much if you ⭐ star the project ⭐ on Github G A new Elementary version (package 0.15.2 CLI 0.15.1) is out and full of cool new stuff 🙌 upgrade by running

dbt deps

and then

dbt run -s elementary

❗ If you upgraded dbt to version 1.8 please upgrade Elementary package and CLI to version this new version ❗ For test samples and failed row count to continue to work, please add the following configuration to your dbt_project.yml:

flags:
 require_explicit_package_overrides_for_builtin_materializations: false

drop corrupt happy New features elementary pink • Group column anomalies by dimension! anomaly detection 🧪 ◦ You can now track column anomalies in a column, segmented by another column! ◦ This is done by adding the newly supported "dimension" param in the column anomalies test ◦ more details here. • Filter dimension anomalies final result table filter ◦ Dimension anomalies results can sometimes be full of insignificant rows containing small dimensions with little data. ◦ To address that issue and avoid getting alerts on these issues we added a new argument to the dimension anomalies test called exclude_final_results • Test execution time in the report ⏲️ ◦ You can find the test execution duration in the test executions page • Models in report dashboard 📊 ◦ Dashboard page now contains widgets showing model errors, failed models and skipped models, so you can see these critical pipeline issues first thing when you open your Elementary report • Singular tests enhancements drop joy ◦ Singular tests in Elementary can now appear in the UI with the table name of your choice! ◦ You can use the configuration here to override the table name with the model of your choice • Trino connector is now supported! 🔌 ◦ Thanks @Tomme for this contribution! drop joy Small fixes 🪲 • Change generate profile args macro name for Athena by @Roman Korsun • Add unique_combination_of_columns to common_tests_configs_mapping by @Yasuhisa Yoshida

@Ella Katz @Itamar Hartstein Please can you confirm who "For test samples and failed row count to continue to work" applies to? Is this specific opt-in/out functionality within elementary or is this some internals and affects everyone? Not clear from message. Thanks

@Adam Cunnington It refers to having samples of rows from your table that failed the test in your test results and alerts

Ok so it affects everyone then?

Everyone who upgraded to dbt 1.8 and are looking at failed row samples. Please see more details here

I stiill don't know what "looking at failed row samples" means. I'm trying to understand which feature/feature set this relates to.

Hi @Adam Cunnington - today when you generate a report using "edr report", Elementary supports showing a sample of rows for failed dbt tests (not anomaly tests - regular dbt tests and expectations). This feature requires the flag above to keep working.

thank you - now clear

Given the dbt vulnerability described here, it would seem unwise to allow all installed packages to override built-in materializations (which is what

require_explicit_package_overrides_for_builtin_materializations: false

would accomplish). Is there a way to only allow the Elementary package to override materializations?

Hi @Brian Waligorski, Thanks for bringing up the article. To your question - We suggested this to dbt as soon as they made the change. They are open for us to contribute this change. We are looking at an alternative until that is done. Regarding the vulnerability in general, we got questions from several users. I shared my approach here: https://www.elementary-data.com/post/are-dbt-packages-secure-the-answer-lies-in-your-dwh-policies

Thank you for the thorough explanation, @Maayan Salom!

I just wanted to follow up and check if there’s been any alternative to setting the flag

require_explicit_package_overrides_for_builtin_materializations: false

for the entire project. How might this flag affect other dbt models or projects within my repository?

i think this is being addressed by dbt in 1.9 if i'm not mistaken

Thanks, that would be nice. I noticed there hasn’t been any recent activity on this issue, so wasnt sure https://github.com/dbt-labs/dbt-core/issues/10090

Hi @Mar, We'll check regarding 1.9, we need to test and see if the sample collection in 1.9 works without the flag and update. Regarding how the flag affects other models - it shouldn't. Elementary dbt package only overrides the test materialization so no models are affected. Not using the flag is also an alternative - Elementary will work, but result samples from tests won't be collected.