Hi there! We've started getting the following alerts on runs:

16:29:46  [WARNING]: Installed package 'elementary' is overriding the built-in
materialization 'table'. Overrides of built-in materializations from installed
packages will be deprecated in future versions of dbt. Please refer to <https://d>
<http://ocs.getdbt.com/reference/global-configs/legacy-behaviors#require_explicit_packag|ocs.getdbt.com/reference/global-configs/legacy-behaviors#require_explicit_packag>
e_overrides_for_builtin_materializations for detailed documentation and
suggested workarounds.

Does elementary have a specific recommendation on how to deal with this or should we create our own override as suggested in the dbt docs?

Hi @Zach Plowman, we're actually about to send an update about this. This is a part of a change in dbt that requires users to explicitly opt-in to enable packages to override materializations. You can override the materializations, but for now we recommend the following simpler measures: For dbt < 1.8: As long as you're using

dbt < 1.8

, Elementary should work just fine and for now you can ignore the warning. Starting from dbt 1.8 (which should be released this week): You can add this to your `dbt_project.yml`:

flags:
  require_explicit_package_overrides_for_builtin_materializations: false

This will still show the warning but Elementary will work as expected. This is a temporary measure. We are working with the dbt team on a proper mechanism to explicitly allow Elementary to override materializations (more details here)

Hi @Itamar Hartstein, thanks for addressing this. I also have the same issue and posted about it above. I'll add the flag for now, but when this is addressed in elementary's next release (I assume), should we remove that flag?

Hey @Mostafa Yazal, this may take a bit longer as it requires a contribution to dbt, but we'll update when this flag can be removed!

Awesome. I'll keep an eye on this and add the flag in the mean time.

Hey @Itamar Hartstein, adding this flag to our dbt 1.7.14 env doesnt seem to be cancelling the warnings. Do you know if that flag is only applicable in dbt 1.8?

Hi @Cooper White! The flag is not supposed to cancel the warnings, as I wrote the warnings will remain until we have a more permanent solution. The flag guarantees the Elementary functionality that depends on overriding materializations will keep working in dbt 1.8.

Ahh ok, my bad - I misunderstood. Thanks!