Hi <@U088WCP3B4P>, my team recently updated to ver...
# ask-elementary-ai
f
Hi @kapa.ai, my team recently updated to version 1.10 of dbt and we now get the following warning:
Copy code
11:19:39  [WARNING]: Installed package 'elementary' is overriding the built-in
materialization 'test'. Overrides of built-in materializations from installed
packages will be deprecated in future versions of dbt. For more information:
<https://docs.getdbt.com/reference/global-configs/legacy-behaviors>
Is there anything we can do to resolve the deprecation warning for built-in materialization overrides
k
A message from kapa.ai
This warning appears because, starting with dbt 1.8, dbt requires users to explicitly allow third-party packages (like Elementary) to override built-in materializations. Elementary does this to enable features such as collecting failed row samples and counts for dbt tests. How to resolve or handle the warning: - Add the following flag to your
dbt_project.yml
file to allow Elementary to override built-in materializations:
Copy code
yaml flags:   require_explicit_package_overrides_for_builtin_materializations: false
This flag is required for Elementary to function correctly with dbt 1.8 and above. However, even after adding this flag, you will still see the warning. This is expected and currently cannot be suppressed. The warning is a temporary measure, and the Elementary team is working with dbt on a longer-term solution. For now, you can safely ignore the warning as long as the flag is set and Elementary features are working as expected. There is no additional action required at this time, and the warning does not indicate a malfunction in Elementary or dbt. More details can be found in the [Elementary troubleshooting documentation](https://docs.elementary-data.com/oss/general/troubleshooting#warning-installed-package-elementary-is-overriding-the-built-in-materialization-xxx) and the [installation guide](https://docs.elementary-data.com/oss/quickstart/quickstart-cli-package#step-by-step-install-elementary-dbt-package). Summary: - Add the flag above to your
dbt_project.yml
. - The warning will persist, but Elementary will work as intended. - No further action is needed until a permanent solution is released by dbt and Elementary. If you have strict CI/CD pipelines that fail on warnings, you may need to adjust your warning/error handling temporarily, as there is currently no way to suppress just this warning in dbt 1.10 and above.