[4:13 PM] <@U088WCP3B4P> 0:33:15 IMPORTANT - Start...
# ask-elementary-ai
s
[4:13 PM] @kapa.ai 103315 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. after defining the macro {% materialization test, default %} {% set result = elementary.materialize_test(dbt.materialization_test_default) %} {% do return(result) %} {% endmaterialization %} and setting the falg to true i still getting like this info. now i think it is not overriding?
k
A message from kapa.ai
Based on the information in the knowledge sources, even after you define a custom test materialization macro and set the flag:
Copy code
yaml flags:   require_explicit_package_overrides_for_builtin_materializations: false
you may still see the warning message about materialization overrides. This is expected behavior for now. The flag allows Elementary to override dbt's built-in materializations (which is required for features like collecting failed row samples and counts), but it does not suppress the warning itself. The warning is a temporary measure and will remain until a more permanent solution is implemented in dbt-core. If you want to mute the warning, you can set the variable
mute_ensure_materialization_override: true
in your
dbt_project.yml
, but according to user reports, this does not always fully suppress the warning in all environments, and it is an open issue being worked on by the Elementary and dbt teams. The functionality should still work as expected as long as the flag is set to `false`—the warning is informational and does not indicate a failure to override materializations or a loss of functionality. You do not need to implement your own override unless you have a specific need to customize the materialization beyond what Elementary provides. For more details, see the official documentation and community discussions: - [Elementary OSS Quickstart: Allowing Elementary to override dbt's default materializations](https://docs.elementary-data.com/oss/quickstart/quickstart-cli-package#important-allowing-elementary-to-override-dbts-default-materializations-relevant-from-dbt-1-8) - [Slack discussion on warning and flag behavior](https://slack.com/archives/C02CTC89LAX/p1715016357916139) - [GitHub issue on warning suppression](https://github.com/elementary-data/elementary/issues/1692) In summary: - The warning is expected and does not mean the override is not working. - The flag enables the required functionality. - Muting the warning is not always effective, but the Elementary team is working on a solution. - You do not need to implement your own override unless you have a custom requirement.