Skip to content

Commit c18df89

Browse files
authored
add ux help (#2815)
1 parent 273e913 commit c18df89

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/guides/custom_materializations.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ SQLMesh supports a variety of [model kinds](../concepts/models/model_kinds.md) t
44

55
There are times, however, when a specific use case doesn't align with any of the supported materialization strategies. For scenarios like this, SQLMesh allows users to create their own materialization implementation using Python.
66

7-
Please note that this is an advanced feature and should only be considered if all other approaches to addressing a use case have been exhausted.
7+
Please note that this is an advanced feature and should only be considered if all other approaches to addressing a use case have been exhausted. If you're at this decision point, we recommend you reach out to our team in the community slack: [here](https://tobikodata.com/community.html)
88

99
## Creating a materialization
1010

@@ -120,6 +120,7 @@ class CustomFullMaterialization(CustomMaterialization):
120120
) -> None:
121121
config_value = model.custom_materialization_properties["config_key"]
122122
# Proceed with implementing the insertion logic.
123+
# Example for existing materialization for look and feel: https://github.com/TobikoData/sqlmesh/blob/main/sqlmesh/core/snapshot/evaluator.py
123124
```
124125

125126
## Packaging custom materializations

0 commit comments

Comments
 (0)