-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
Fix dangling datediff reference #233
Conversation
FYI this just nuked some incrementals with the following error. I'm sure it's a quick fix on our end to adjust the test we use for recency checks, but just a heads up @clausherther (At least I am assuming it was this based on timing, only just investigating now)
|
Hmm this only fixed the ref for datediff to be explicit, so instead of calling dbt-core |
If anything, I would have been this commit which is in 0.8.1 3df4494 |
Yea, it may have been that one as the hourly incremental at 12 eastern is what started failing. Jumped a bit early to this one. |
If you wouldn't mind, please open a BUG issue. This shouldn't happen if you're on dbt >= 1.2 I think. |
Yea, once we get the issue fixed I can ticket what happened. |
Either hard-coding to 0.8.0 or bumping up to dbt 1.3.0 addresses the error |
Interesting, I was under the impression the date macros were all in 1.2+, but tbh we're not explicitly testing the CI pipeline for 1.2. I'll take a look, but have a feeling we won't revert the release but instead clarify the dbt version dependency. |
I can't reproduce on dbt 1.2, I have a feeling you might have some other cross-package issues with dbt-utils maybe. |
Likely a cross dependency like that, we'll have to address in greater detail when everyone is back next week. Appreciate your responsiveness! |
We pushed a couple of updates to dbt-date and dbt-expectations that should help with issues related to also including dbt-utils. Let me know if that fixes things for you. |
No description provided.