shobia
11/19/2025, 11:19 AMtests config has been renamed to data_tests. Please see
https://docs.getdbt.com/docs/build/data-tests#new-data_tests-syntax for more
information.
111616 [WARNING]: Did not find matching node for patch with name 'query_monitoring_live__common_refined4' in the 'models' section of file 'models\_sources\_source_redshift.yml'
111616 [WARNING]: Did not find matching node for patch with name 'query_monitoring_history__common_refined4' in the 'models' section of file 'models\_sources\_source_redshift.yml'
111616 [WARNING]: Test 'test.pem_dbt.not_null_query_monitoring_live__common_refined4_query.7b0880b1b9' (models\_sources\_source_redshift.yml) depends on a node named 'query_monitoring_live__common_refined4' in package '' which was not found
111616 [WARNING]: Test 'test.pem_dbt.not_null_query_monitoring_live__common_refined4_starttime.285023cce4' (models\_sources\_source_redshift.yml) depends on a node named 'query_monitoring_live__common_refined4' in package '' which was not found
111616 [WARNING]: Test 'test.pem_dbt.not_null_query_monitoring_history__common_refined4_query.ef137e8ed5' (models\_sources\_source_redshift.yml) depends on a node named 'query_monitoring_history__common_refined4' in package '' which was not found
111616 [WARNING]: Test 'test.pem_dbt.not_null_query_monitoring_history__common_refined4_starttime.a0d9de1c83' (models\_sources\_source_redshift.yml) depends on a node named 'query_monitoring_history__common_refined4' in package '' which was not found
111617 Found 761 models, 4 seeds, 4 operations, 746 data tests, 460 sources, 1327 macros
111617
111627
111627 Running 2 on-run-start hooks
111627 INFO: macro on_run_start skipped because schema not dbt_main, dbt_uat or dbt_prod
111627 1 of 2 START hook: pem_dbt.on-run-start.0 ...................................... [RUN]
111627 1 of 2 OK hook: pem_dbt.on-run-start.0 ......................................... [OK in 0.00s]
111627
IMPORTANT - Starting from dbt 1.8, users must explicitly allow packages to override materializations.
Elementary requires this ability to support collection of samples and failed row count for dbt tests.
Please add the following flag to dbt_project.yml to allow it:
flags:
require_explicit_package_overrides_for_builtin_materializations: false
Notes -
* This is a temporary measure that will result in a deprecation warning, please ignore it for now. Elementary is working with the dbt-core team on a more permanent solution.
* This message can be muted by setting the 'mute_ensure_materialization_override' var to true.
111627 2 of 2 START hook: elementary.on-run-start.0 ................................... [RUN]
111627 2 of 2 OK hook: elementary.on-run-start.0 ...................................... [OK in 0.00s]
111627
111627 Concurrency: 10 threads (target='main')
111627
111627 1 of 5 START test elementary_column_anomalies_item_branch__parquet_common_refined4_both__2__null_count__itembranch_creation_date__3__3__current_date [RUN]
111627 2 of 5 START test elementary_column_anomalies_item_branch__parquet_common_refined4_both__2__null_percent__itembranch_creation_date__3__3__current_date [RUN]
111627 3 of 5 START test elementary_volume_anomalies_item_branch__parquet_common_refined4_both__1__1 [RUN]
111627 4 of 5 START test not_null_item_branch__parquet_common_refined4__itembranchskey_ [RUN]
111627 5 of 5 START test unique_item_branch__parquet_common_refined4__itembranchskey_ . [RUN]
111627 Elementary: Started running data monitors on: PROD.DBT_SHOBIA_COMMON_REFINED4.ITEM_BRANCH__PARQUET_COMMON_REFINED4
111627 USING CUSTOM TEST MATERIALIZATION OVERRIDE
111627 USING CUSTOM TEST MATERIALIZATION OVERRIDE
111629 4 of 5 PASS not_null_item_branch__parquet_common_refined4__itembranchskey_ ..... [PASS in 2.09s]
111631 Elementary: Started running data monitors on: PROD.DBT_SHOBIA_COMMON_REFINED4.ITEM_BRANCH__PARQUET_COMMON_REFINED4 itembranch.creation date
111631 Elementary: Started running data monitors on: PROD.DBT_SHOBIA_COMMON_REFINED4.ITEM_BRANCH__PARQUET_COMMON_REFINED4 itembranch.creation date
111632 Elementary: Finished running data monitors on: PROD.DBT_SHOBIA_COMMON_REFINED4.ITEM_BRANCH__PARQUET_COMMON_REFINED4
111633 USING CUSTOM TEST MATERIALIZATION OVERRIDE
111633 3 of 5 PASS elementary_volume_anomalies_item_branch__parquet_common_refined4_both__1__1 [PASS in 5.87s]
111635 5 of 5 PASS unique_item_branch__parquet_common_refined4__itembranchskey_ ....... [PASS in 7.70s]
111637 Elementary: Finished running data monitors on: PROD.DBT_SHOBIA_COMMON_REFINED4.ITEM_BRANCH__PARQUET_COMMON_REFINED4 itembranch.creation date
111637 USING CUSTOM TEST MATERIALIZATION OVERRIDE
111638 1 of 5 PASS elementary_column_anomalies_item_branch__parquet_common_refined4_both__2__null_count__itembranch_creation_date__3__3__current_date [PASS in 10.66s]
111638 Elementary: Finished running data monitors on: PROD.DBT_SHOBIA_COMMON_REFINED4.ITEM_BRANCH__PARQUET_COMMON_REFINED4 itembranch.creation date
111638 USING CUSTOM TEST MATERIALIZATION OVERRIDE
111638 2 of 5 PASS elementary_column_anomalies_item_branch__parquet_common_refined4_both__2__null_percent__itembranch_creation_date__3__3__current_date [PASS in 11.13s]
111638
111638 Running 2 on-run-end hooks
111638 INFO: macro on_run_end skipped because schema not dbt_main, dbt_uat or dbt_prod
111638 1 of 2 START hook: pem_dbt.on-run-end.0 ........................................ [RUN]
111638 1 of 2 OK hook: pem_dbt.on-run-end.0 ........................................... [OK in 0.00s]
111656 2 of 2 START hook: elementary.on-run-end.0 ..................................... [RUN]
111656 2 of 2 OK hook: elementary.on-run-end.0 ........................................ [OK in 0.00s]
111656
111656
111656 Finished running 5 data tests, 4 project hooks in 0 hours 0 minutes and 38.96 seconds (38.96s).
111657
111657 Completed successfully
111657
111657 Done. PASS=5 WARN=0 ERROR=0 SKIP=0 TOTAL=5
PS V:\pem_dbt>
so it is picking the macro , but then why do it suggest like setting it to false even now the dbt elementray is overriding the info says like
IMPORTANT - Starting from dbt 1.8, users must explicitly allow packages to override materializations.
Elementary requires this ability to support collection of samples and failed row count for dbt tests.
Please add the following flag to dbt_project.yml to allow it:
flags:
require_explicit_package_overrides_for_builtin_materializations: false
Notes -
* This is a temporary measure that will result in a deprecation warning, please ignore it for now. Elementary is working with the dbt-core team on a more permanent solution.
* This message can be muted by setting the 'mute_ensure_materialization_override' var to true.
now that i defined explicitly allow packages to override materializations. explicitly using macros still why does it say like thiskapa.ai
11/19/2025, 11:19 AMkapa.ai
11/19/2025, 11:19 AMtest materialization is currently working. A few key points from the docs and Slack threads: - Starting with dbt 1.8, package overrides of built‑in materializations (like test) are effectively blocked unless you set: yaml flags: require_explicit_package_overrides_for_builtin_materializations: false Elementary relies on overriding the test materialization to collect samples and failed row counts for dbt tests. [[Troubleshooting](https://docs.elementary-data.com/oss/general/troubleshooting#warning-installed-package-elementary-is-overriding-the-built-in-materialization-xxx)] - That’s why Elementary emits the “IMPORTANT – Starting from dbt 1.8…” message: to remind you that, without this flag, its materialization override may stop working as dbt tightens enforcement. - The fact that you see USING CUSTOM TEST MATERIALIZATION OVERRIDE in your logs just confirms that your own custom test materialization macro is being picked up at runtime (per dbt’s standard override rules), not that dbt will continue to allow package overrides in all future 1.8+ behavior without that flag. Community members are already seeing deprecation warnings and inconsistent behavior around these overrides, and Elementary calls this out as an open issue they’re working on with dbt-core. [[Slack 1729523…](https://slack.com/archives/C02CTC89LAX/p1729523466778279)] - You can mute the message (but not the underlying dbt deprecation warning) by setting: yaml vars: mute_ensure_materialization_override: true Note that several users report still seeing some warnings even with this var set; it’s documented as a known open issue. [[Slack 1727244…](https://slack.com/archives/C02CTC89LAX/p1727244860265519)] So, in short: Elementary is warning you proactively because dbt 1.8 requires explicit allowance for package materialization overrides; your override appears to work now, but the message is about ensuring that behavior remains supported and that Elementary can reliably capture test samples/failed-row counts going forward.