<@U088WCP3B4P> How to disable metadata tables in E...
# ask-elementary-ail
Luiz Felipe Campos da Silva
12/08/2025, 2:11 PM@kapa.ai How to disable metadata tables in Elementary hooks? Just like dbt_models or dbt_columns
k
kapa.ai
12/08/2025, 2:11 PMA message from kapa.ai
kapa.ai
12/08/2025, 2:11 PMYou can disable Elementary’s metadata updates (including
dbt_modelsdbt_columnsvarsdbt_project.ymlon-run-enddbt_modelsdbt_testsdbt_sources Copy code
yml vars: disable_dbt_artifacts_autoupload: true Copy code
bash dbt run --select elementary.edr.dbt_artifactsdbt_columns Copy code
yml vars: disable_dbt_columns_autoupload: truedbt_columns Copy code
yml models: elementary: edr: dbt_artifacts: dbt_columns: +enabled: false metadata_store: +enabled: false # disables all metadata_store models, incl. filtered_information_schema_*filtered_information_schema_columns Copy code
yml models: elementary: edr: metadata_store: filtered_information_schema_columns: +enabled: falsedisable_dbt_artifacts_autouploaddisable_dbt_columns_autoupload+enabled: falsel
Luiz Felipe Campos da Silva
12/08/2025, 2:16 PM Copy code
disable_dbt_artifacts_autoupload: truek
kapa.ai
12/08/2025, 2:16 PMA message from kapa.ai
kapa.ai
12/08/2025, 2:16 PMNo, setting
Copy code
yml vars: disable_dbt_artifacts_autoupload: truedbt_modelsdbt_testsdbt_sourcesdbt_columnsrun_resultselementary_test_results Copy code
yml vars: disable_run_results: true disable_tests_results: true disable_dbt_invocation_autoupload: truel
Luiz Felipe Campos da Silva
12/08/2025, 3:37 PM@kapa.ai Why my packages configurations are having more importance when the views are built?
k
kapa.ai
12/08/2025, 3:38 PMA message from kapa.ai
kapa.ai
12/08/2025, 3:38 PMIn dbt, configs defined inside a package’s own
dbt_project.ymldbt_project.ymldbt_project.ymlelementarymy_project.elementaryelementary Copy code
yml models: academia: elementary: +schema: elementary # applies to academia/elementary, not the package Copy code
yml models: elementary: +schema: elementary # this targets the package academia: # your project’s models…models:materialized: table Copy code
yml models: my_project: materialized: "{{ 'table' if target.name == 'prod-cloud' else 'view' }}" elementary: +schema: "elementary"models: materialized: tabledbt_project.yml Copy code
yml models: my_project: # your project name materialized: view # or your logic elementary: +schema: elementarydbt_project.ymldbt_project.ymll
Luiz Felipe Campos da Silva
12/08/2025, 3:41 PM@kapa.ai name: 'elementary_test2'
version: '1.0.0'
config-version: 2
# This setting configures which "profile" dbt uses for this project.
profile: 'elementary_test2'
# These configurations specify where dbt should look for different types of files.
# For Databricks asset bundles, we put everything in src, as you may have
# non-dbt resources in your project.
model-paths: ["src/models"]
analysis-paths: ["src/analyses"]
test-paths: ["src/tests"]
seed-paths: ["src/seeds"]
macro-paths: ["src/macros"]
snapshot-paths: ["src/snapshots"]
clean-targets: # directories to be removed by
dbt clean{{ config(...) }} Copy code
from
`platform`.`general_elementary_metrics`.`dbt_invocations`k
kapa.ai
12/08/2025, 3:41 PMA message from kapa.ai
kapa.ai
12/08/2025, 3:42 PMYour
elementarygenerate_schema_namegeneral_elementary_metricsmodels: Copy code
yml models: +persist_docs: relation: true columns: true elementary_test2: example: +materialized: view elementary +schema: metrics +enabled: "{{ target.name in ('prod') and var('ELEMENTARY_ENABLED', true) }}" edr: dbt_artifacts: +enabled: "{{var('ARTIFACTS_ENABLED', false)}}"elementary Copy code
yml models: +persist_docs: relation: true columns: true elementary_test2: example: +materialized: view elementary: # <- colon, same level as elementary_test2 +schema: metrics +enabled: "{{ target.name in ('prod') and var('ELEMENTARY_ENABLED', true) }}" edr: dbt_artifacts: +enabled: "{{ var('ARTIFACTS_ENABLED', false) }}"models:dbt_project.ymljob_run_results Copy code
bash dbt run --select elementarygenerate_schema_nameelementaryelementaryplatform.general_elementary_metricsgenerate_schema_namemodels: elementary: ...node.package_name == 'elementary'general_elementary_metricsnode.package_name == 'elementary'l
Luiz Felipe Campos da Silva
12/08/2025, 3:43 PM@kapa.ai I'm sorry I send you the wrong code block, It's actually with this colon, the problem is not related to this, macros_nexus schema is still wining
k
kapa.ai
12/08/2025, 3:43 PMA message from kapa.ai
kapa.ai
12/08/2025, 3:44 PMYour issue matches the pattern where a custom schema macro is still controlling Elementary models, even though the
models: elementary:elementary Copy code
yml models: elementary: +schema: elementarygenerate_schema_nameTRANSFORMED_*general_elementary_metricsnode.package_name == 'elementary'+schema:generate_schema_name Copy code
jinja {% macro generate_schema_name(custom_schema_name, node) -%} {%- set default_schema = target.schema -%} {% if node.package_name == 'elementary' and custom_schema_name %} {{ default_schema }}_{{ custom_schema_name | trim }} {% else %} {{ generate_schema_name_for_env(custom_schema_name, node) }} {% endif %} {%- endmacro %}node.package_name == 'elementary'..._elementaryTRANSFORMED_*general_elementary_metrics Copy code
bash dbt run --select elementarymodels: elementary: +schema: metricsl
Luiz Felipe Campos da Silva
12/08/2025, 3:46 PM@kapa.ai I don't think that would help like look at my macro:
{% macro generate_schema_name(custom_schema_name, node) -%}
{%- set default_schema = target.schema -%}
{%- if custom_schema_name is none or custom_schema_name | trim == '' -%}
{{ default_schema }}
{%- elif custom_schema_name | trim == 'general_elementary_metrics'-%}
{{ custom_schema_name | trim }}
{%- else -%}
{{ default_schema }}_{{ custom_schema_name | trim }}
{%- endif -%}
{%- endmacro %}
k
kapa.ai
12/08/2025, 3:46 PMA message from kapa.ai
kapa.ai
12/08/2025, 3:46 PMYour macro is forcing
general_elementary_metrics+schema: metrics Copy code
jinja {% macro generate_schema_name(custom_schema_name, node) -%} {%- set default_schema = target.schema -%} {%- if custom_schema_name is none or custom_schema_name | trim == '' -%} {{ default_schema }} {%- elif custom_schema_name | trim == 'general_elementary_metrics'-%} {{ custom_schema_name | trim }} # <- hard‑codes schema "general_elementary_metrics" {%- else -%} {{ default_schema }}_{{ custom_schema_name | trim }} {%- endif -%} {%- endmacro %}dbt_project.yml Copy code
yml models: elementary: +schema: metricscustom_schema_namemetricselse{{ default_schema }}_metricsdummy_dbt2_metricsgeneral_elementary_metricsgenerate_schema_name+schema: Copy code
jinja {% macro generate_schema_name(custom_schema_name, node) -%} {%- set default_schema = target.schema -%} {% if node.package_name == 'elementary' and custom_schema_name %} {# respect the +schema on Elementary models (e.g. "metrics") #} {{ custom_schema_name | trim }} {% elif custom_schema_name is none or custom_schema_name | trim == '' -%} {{ default_schema }} {% elif custom_schema_name | trim == 'general_elementary_metrics'-%} {{ custom_schema_name | trim }} {% else -%} {{ default_schema }}_{{ custom_schema_name | trim }} {% endif %} {%- endmacro %}generate_schema_namenode.package_name == 'elementary' Copy code
bash dbt run --select elementarygeneral_elementary_metricsFROMjob_run_resultscustom_schema_namel
Luiz Felipe Campos da Silva
12/08/2025, 4:11 PM@kapa.ai This variable exists? elementary_database: "platform"
elementary_schema: "dummy_dbt2_metrics"
They can fix my problem?\
k
kapa.ai
12/08/2025, 4:11 PMA message from kapa.ai
kapa.ai
12/08/2025, 4:11 PMThose exact variables (
elementary_databaseelementary_schemadbt_project.yml Copy code
yml models: elementary: +database: <your_database> +schema: <your_schema>elementaryelementary_databaseelementary_schema+database+schemamodels: elementary:dbt_project.ymlgenerate_schema_nameelementarymodels: elementary:l
Luiz Felipe Campos da Silva
12/08/2025, 4:39 PM@kapa.ai How to disable only the elementary views from being enabled in dbt_project.yml?
k
kapa.ai
12/08/2025, 4:40 PMA message from kapa.ai
kapa.ai
12/08/2025, 4:40 PMYou can’t target only “views” as a group in Elementary from the docs we have, but you can disable specific Elementary models (including the ones that are materialized as views) via normal dbt model configs in
dbt_project.yml Copy code
yml models: elementary: edr: metadata_store: filtered_information_schema_tables: +enabled: false filtered_information_schema_columns: +enabled: false dbt_artifacts: dbt_models: +enabled: false dbt_columns: +enabled: false+enabled: falseinformation_schemaschema_changes Copy code
yml models: elementary: +schema: elementary edr: +enabled: "{{ var('enable_elementary_models', false) }}" Copy code
bash dbt run --select elementary --vars '{"enable_elementary_models": true}'l
Luiz Felipe Campos da Silva
12/08/2025, 8:00 PM@kapa.ai Can I have a package that has models with the same name from the elementary?
k
kapa.ai
12/08/2025, 8:00 PMA message from kapa.ai
kapa.ai
12/08/2025, 8:01 PMYes, you can have models in your own package/project with the same names as Elementary models, but you need to avoid conflicting them in the same schema and namespace. From the docs and Slack threads, Elementary is just another dbt package, so its models are addressed by package path, e.g.
elementary.edr.dbt_run_resultsmodels: elementary: Copy code
yml models: my_project: # your models elementary: +schema: elementary # or a dedicated schema like <target_schema>_elementary39 Views