feat(snowflake): add scheduler support for dynamic tables by igorbelianski-cyber · Pull Request #1710 · dbt-labs/dbt-adapters

igorbelianski-cyber · 2026-03-04T02:10:32Z

Add support for the Snowflake dynamic table scheduler property, which controls whether the internal refresh scheduler is ENABLE or DISABLE. This is distinct from scheduling_state (ACTIVE/SUSPENDED), which is a Snowflake-managed runtime status.

Key changes:

Add Scheduler enum (ENABLE/DISABLE) and make target_lag optional in SnowflakeDynamicTableConfig to support scheduler=DISABLE without a target lag specification.
Apply implicit scheduler defaults in both parse_relation_config and parse_relation_results: when scheduler is not explicitly set, default to ENABLE if target_lag is present, DISABLE otherwise. This aligns the Python-side change detection logic with the Jinja macro defaults.
Add scheduler change detection in dynamic_table_config_changeset and prevent target_lag from being included in ALTER when its new value is None (avoids generating target_lag = 'None' in SQL).
Update CREATE, REPLACE, and ALTER macros to render scheduler in DDL with correct ENABLE/DISABLE defaults. Guard ALTER target_lag rendering to skip when context is None.
Update materialization to issue ALTER DYNAMIC TABLE ... REFRESH when scheduler is DISABLE (explicit or implicit via missing target_lag), since Snowflake won't auto-refresh in that case.
Read the scheduler column from SHOW DYNAMIC TABLES when available.
Fix FileSystemLoader in test_alter_relation_comment_macro.py to use an absolute path, avoiding TemplateNotFound errors from different CWDs.
Add comprehensive unit tests for scheduler config parsing, changeset detection, and change detection logic, plus functional tests covering scheduler in CREATE/ALTER/REPLACE DDL and refresh behavior.

Made-with: Cursor

resolves #
docs dbt-labs/docs.getdbt.com/#

Problem

Solution

Checklist

I have read the contributing guide and understand what's expected of me
I have run this code in development and it appears to resolve the stated issue
This PR includes tests, or tests are not required/relevant for this PR
This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

Add support for the Snowflake dynamic table `scheduler` property, which controls whether the internal refresh scheduler is ENABLE or DISABLE. This is distinct from `scheduling_state` (ACTIVE/SUSPENDED), which is a Snowflake-managed runtime status. Key changes: - Add `Scheduler` enum (ENABLE/DISABLE) and make `target_lag` optional in `SnowflakeDynamicTableConfig` to support scheduler=DISABLE without a target lag specification. - Apply implicit scheduler defaults in both `parse_relation_config` and `parse_relation_results`: when scheduler is not explicitly set, default to ENABLE if target_lag is present, DISABLE otherwise. This aligns the Python-side change detection logic with the Jinja macro defaults. - Add scheduler change detection in `dynamic_table_config_changeset` and prevent target_lag from being included in ALTER when its new value is None (avoids generating `target_lag = 'None'` in SQL). - Update CREATE, REPLACE, and ALTER macros to render `scheduler` in DDL with correct ENABLE/DISABLE defaults. Guard ALTER target_lag rendering to skip when context is None. - Update materialization to issue `ALTER DYNAMIC TABLE ... REFRESH` when scheduler is DISABLE (explicit or implicit via missing target_lag), since Snowflake won't auto-refresh in that case. - Read the `scheduler` column from SHOW DYNAMIC TABLES when available. - Fix FileSystemLoader in test_alter_relation_comment_macro.py to use an absolute path, avoiding TemplateNotFound errors from different CWDs. - Add comprehensive unit tests for scheduler config parsing, changeset detection, and change detection logic, plus functional tests covering scheduler in CREATE/ALTER/REPLACE DDL and refresh behavior. Made-with: Cursor

github-actions · 2026-03-11T21:48:28Z

Thank you for your pull request! We could not find a changelog entry for this change in the dbt-snowflake package. For details on how to document a change, see the Contributing Guide.

colin-rogers-dbt · 2026-03-16T22:29:24Z

dbt-snowflake/src/dbt/adapters/snowflake/relation_configs/dynamic_table.py

+        if scheduler := relation_config.config.extra.get("scheduler"):  # type:ignore
+            config_dict["scheduler"] = scheduler.upper()
+        elif config_dict.get("target_lag"):
+            config_dict["scheduler"] = "ENABLE"


Can we use the enum values?

colin-rogers-dbt · 2026-03-16T22:29:35Z

dbt-snowflake/src/dbt/adapters/snowflake/relation_configs/dynamic_table.py

+        scheduler = dynamic_table.get("scheduler")
+        target_lag = dynamic_table.get("target_lag")
+        if scheduler is None:
+            scheduler = "ENABLE" if target_lag else "DISABLE"


Same as above

colin-rogers-dbt · 2026-03-16T22:30:37Z

dbt-snowflake/src/dbt/adapters/snowflake/relation_configs/dynamic_table.py

    query: str
-    target_lag: str
    snowflake_warehouse: str
+    target_lag: Optional[str] = None


target_lag is still required if scheduler is enabled right? We should raise a validation exception in that case.

target lag is not mandatory any more
with scheduler = DISABLED , target_lag will not be allowed ( we treat dynamic tables as a unit of incrementalization and completely disconnected from the dynamic table built in scheduler)
with scheduler = ENABLED it is target lag is still mandatory

PS
i was debating whether DBT needs to validate it as opposed allowing snowflake to produce appropriate precise error ( implementing it here seem like extra validation effort that doesn't add a lot of value and make chnages (if snowflake adds some new modes hard to version)

colin-rogers-dbt · 2026-03-16T22:34:49Z

dbt-snowflake/src/dbt/adapters/snowflake/relation_configs/dynamic_table.py

        return cls("ON_CREATE")


+class Scheduler(StrEnum):


I wonder if there's actually three states:

DISABLE - we don't want the MV to be updated

ENABLE - require target_lag (default state today

MANUAL - dbt runs the refresh manually on every run

There are 2 states:
ENABLE ( default like Dynamic TAbles /MV ) work today subject to be scheduled by Snowflake directly or part of the downstream schedule
DISABLED ( only manual refreshes allowed , Dynamic table scheduler will never touch it. directly or through upstream dependency). => DT's

i do not see a meaningful scenario to justify 3rd mode where we want to disable Dynamic tables from both DBT refreshes and Snowflake Dynamic table scheduler.
( i guess target_lag = downstream on all DTs in the pipeline achieves similar effect functionally , but i am not seeing meaningful scenario for that case)

moreover 2 modes provide really simple syntax for users ( they just need to specify warehouse, absence of target lag implies disabling Dynmic table scheduler and DBT running refreshes)

igorbelianski-cyber requested a review from a team as a code owner March 4, 2026 02:10

cla-bot bot added the cla:yes The PR author has signed the CLA label Mar 4, 2026

igorbelianski-cyber force-pushed the ibelianski-snowflake-dynamic-table-schedile-singleton-clean branch from a4393d5 to 3b2447d Compare March 4, 2026 02:12

add test coverage

09f35e2

colin-rogers-dbt added the ci:approve-public-fork-ci label Mar 11, 2026

colin-rogers-dbt temporarily deployed to dbt-snowflake March 11, 2026 21:48 — with GitHub Actions Inactive

pre-commit run --all-files

309d6a5

github-actions bot removed the ci:approve-public-fork-ci label Mar 11, 2026

colin-rogers-dbt added the ci:approve-public-fork-ci label Mar 12, 2026

colin-rogers-dbt temporarily deployed to dbt-snowflake March 12, 2026 18:32 — with GitHub Actions Inactive

feature description

2bb2bed

github-actions bot removed the ci:approve-public-fork-ci label Mar 12, 2026

colin-rogers-dbt added the ci:approve-public-fork-ci label Mar 12, 2026

colin-rogers-dbt temporarily deployed to dbt-snowflake March 12, 2026 23:31 — with GitHub Actions Inactive

colin-rogers-dbt reviewed Mar 16, 2026

View reviewed changes

PR feedback

d9454a6

github-actions bot removed the ci:approve-public-fork-ci label Mar 17, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(snowflake): add scheduler support for dynamic tables #1710

feat(snowflake): add scheduler support for dynamic tables #1710
igorbelianski-cyber wants to merge 5 commits intodbt-labs:mainfrom
igorbelianski-cyber:ibelianski-snowflake-dynamic-table-schedile-singleton-clean

igorbelianski-cyber commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 11, 2026

Uh oh!

colin-rogers-dbt Mar 16, 2026

Uh oh!

igorbelianski-cyber Mar 17, 2026

Uh oh!

colin-rogers-dbt Mar 16, 2026

Uh oh!

igorbelianski-cyber Mar 17, 2026

Uh oh!

colin-rogers-dbt Mar 16, 2026

Uh oh!

igorbelianski-cyber Mar 17, 2026 •

edited

Loading

Uh oh!

colin-rogers-dbt Mar 16, 2026

Uh oh!

igorbelianski-cyber Mar 17, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

igorbelianski-cyber commented Mar 4, 2026

Problem

Solution

Checklist

Uh oh!

github-actions bot commented Mar 11, 2026

Uh oh!

colin-rogers-dbt Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

igorbelianski-cyber Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

colin-rogers-dbt Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

igorbelianski-cyber Mar 17, 2026

Choose a reason for hiding this comment

Uh oh!

colin-rogers-dbt Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

igorbelianski-cyber Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

colin-rogers-dbt Mar 16, 2026

Choose a reason for hiding this comment

Uh oh!

igorbelianski-cyber Mar 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

igorbelianski-cyber Mar 17, 2026 •

edited

Loading

igorbelianski-cyber Mar 17, 2026 •

edited

Loading