Document skip_optimize model config for dbt-databricks#9496
Open
moomindani wants to merge 1 commit into
Open
Conversation
Co-authored-by: Isaac
|
@moomindani is attempting to deploy a commit to the dbt-labs Team on Vercel. A member of the Team first needs to authorize it. |
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
dbt-databricks 1.12.2 adds a new
skip_optimizemodel config that lets you opt a model out of the post-materializationOPTIMIZEcall while keepingzorder/liquid_clustered_by/auto_liquid_clusterin the table definition. This documents it on the Databricks configurations page.It complements the existing run-wide
DATABRICKS_SKIP_OPTIMIZEvariable by allowing per-model (and, via config inheritance, per-folder / per-project) opt-out. The added note also clarifies the precedence:DATABRICKS_SKIP_OPTIMIZE=trueskipsOPTIMIZEfor every model and cannot be re-enabled for an individual model withskip_optimize: false.Related: dbt-databricks PR databricks/dbt-databricks#1485, issue databricks/dbt-databricks#703
Checklist