From d92b9f5ea73123398b4a8f73bcbe19437a677b3b Mon Sep 17 00:00:00 2001 From: mirnawong1 <89008547+mirnawong1@users.noreply.github.com> Date: Wed, 24 Jan 2024 13:05:48 +0000 Subject: [PATCH] update to add links and add clarity on model contrcts support adding links to clarify or add context on operations and the run operation command. also adding info on model contracts and its relation to ephemeral materialization [per feedback](https://getdbt.slack.com/archives/C0441GSRU04/p1705684634213419) --- website/docs/docs/build/materializations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/docs/docs/build/materializations.md b/website/docs/docs/build/materializations.md index 9ae6021cc71..f07c3e03928 100644 --- a/website/docs/docs/build/materializations.md +++ b/website/docs/docs/build/materializations.md @@ -100,8 +100,9 @@ When using the `table` materialization, your model is rebuilt as a 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