Skip to content

Commit

Permalink
This branch was auto-updated!
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] authored Jan 24, 2024
2 parents 1bf7e5b + 0e52326 commit 21071f2
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion website/docs/docs/build/materializations.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,8 +100,9 @@ When using the `table` materialization, your model is rebuilt as a <Term id="tab
- Ephemeral models can help keep your <Term id="data-warehouse" /> clean by reducing clutter (also consider splitting your models across multiple schemas by [using custom schemas](/docs/build/custom-schemas)).
* **Cons:**
* You cannot select directly from this model.
* Operations (e.g. macros called via `dbt run-operation` cannot `ref()` ephemeral nodes)
* [Operations](/docs/build/hooks-operations#about-operations) (for example, macros called using [`dbt run-operation`](/reference/commands/run-operation) cannot `ref()` ephemeral nodes)
* Overuse of ephemeral materialization can also make queries harder to debug.
* Ephemeral materialization doesn't support [model contracts](/docs/collaborate/govern/model-contracts#where-are-contracts-supported).
* **Advice:** Use the ephemeral materialization for:
* very light-weight transformations that are early on in your DAG
* are only used in one or two downstream models, and
Expand Down

0 comments on commit 21071f2

Please sign in to comment.