Support the volatility config of function nodes #1414
+402
−15
Conversation
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
…nsure we get `EventCatcher` from package
QMalcolm
commented
Oct 29, 2025
| {% if model.config.get('volatility') == 'deterministic' %} | ||
| IMMUTABLE | ||
| {% elif model.config.get('volatility') == 'stable' %} | ||
| {% do exceptions.raise_compiler_error("`Stable` function volatility is not supported for Snowflake") %} |
There was a problem hiding this comment.
Alternatively we could
- Ignore
stable - Raise a warning
The benefit of doing so would be that switching a project from another data warehouse to snowflake wouldn't break functions declared "stable". The drawback of not raising an error is that a user might set stable for a function in snowflake, think doing so is doing so does something, but it doesn't 🤔
cc: @graciegoheen
There was a problem hiding this comment.
Relatedly, in dbt-bigquery we're just ignoring volatility. What we decided to do with stable in dbt-snowflake is also what we should do with any volatility setting in dbt-bigquery
QMalcolm
force-pushed
the
qmalcolm--1345-begin-templating-volatility-for-scalar-functions
branch
from
36e15ee to
52aeb96
Compare
QMalcolm
had a problem deploying
to
dbt-snowflake
GitHub Actions
Error
QMalcolm
temporarily deployed
to
dbt-snowflake
GitHub Actions
Inactive
QMalcolm
had a problem deploying
to
dbt-redshift
GitHub Actions
Failure
QMalcolm
had a problem deploying
to
dbt-bigquery
GitHub Actions
Failure
QMalcolm
requested a deployment
to
dbt-spark
GitHub Actions
In progress
QMalcolm
requested a deployment
to
dbt-spark
GitHub Actions
In progress
QMalcolm
requested a deployment
to
dbt-bigquery
GitHub Actions
In progress
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.
resolves #1345
Problem
dbt-core added the ability to set function node volatility in dbt-labs/dbt-core#12100. Thus in adapters we needed to begin interpolating the correct volatility value into the function materialization macros.
Solution
Checklist