Skip to content

dbt: Add cluster AUTO SCALING STRATEGY (hydration burst) support DEX-67#37800

Open
bobbyiliev wants to merge 5 commits into
MaterializeInc:mainfrom
bobbyiliev:dbt-cluster-auto-scaling-strategy
Open

dbt: Add cluster AUTO SCALING STRATEGY (hydration burst) support DEX-67#37800
bobbyiliev wants to merge 5 commits into
MaterializeInc:mainfrom
bobbyiliev:dbt-cluster-auto-scaling-strategy

Conversation

@bobbyiliev

@bobbyiliev bobbyiliev commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Adds support for the Materialize v26.34 AUTO SCALING STRATEGY (hydration burst) cluster option to the dbt-materialize adapter. The create_cluster operation accepts a new auto_scaling_strategy argument, a new alter_cluster_auto_scaling_strategy operation sets or resets the strategy on an existing cluster (including the RESET and empty = () disable forms), and deploy_init now copies the production cluster's strategy to the _dbt_deploy cluster so blue/green deployment environments hydrate faster ahead of cutover. Validation mirrors the server-side rules (managed clusters only, MANUAL schedule only, hydration size must differ from the steady size) with clear compile-time errors.

@bobbyiliev
bobbyiliev marked this pull request as ready for review July 22, 2026 10:49
@bobbyiliev
bobbyiliev requested a review from a team as a code owner July 22, 2026 10:49
@bobbyiliev
bobbyiliev requested review from def-, jubrad and sjwiesman July 22, 2026 10:49

@def- def- left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding tests! I don't know enough about dbt to judge the rest

@bobbyiliev bobbyiliev changed the title dbt: Add cluster AUTO SCALING STRATEGY (hydration burst) support dbt: Add cluster AUTO SCALING STRATEGY (hydration burst) support DEX-67 Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants