-
Notifications
You must be signed in to change notification settings - Fork 943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add dbt_valid_to_current #6308
base: current
Are you sure you want to change the base?
add dbt_valid_to_current #6308
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@mirnawong1 grouping your outstanding questions into a handful of categories: Hardcoded SQL expressionsQuestion:
👍 Hardcoded expressions that work within the data platform is the only option that is available currently. The precise syntax will vary per warehouse, so Jinja within
|
@mirnawong1 I added the |
adding new config for
dbt_valid_to_current
, which allows users to set a future date fordbt_valid_to
using the dbt_valid_to_current config in yaml/config/project.Resolves #6275
Outstanding questions:
dbt_valid_to_current: '9999, 12, 31'
) or must they useto_date
?var
to return a SQL statement '{{ var('my_future_date') }}'🚀 Deployment available! Here are the direct links to the updated files: