-
Notifications
You must be signed in to change notification settings - Fork 98
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
Engine-specific rendering for sub-daily granularity options #1258
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The BigQuery update will not work as expected for sub-daily granularities. To be honest I don't know what'll happen when you put a DATETIME in there, probably a type mismatch error.
@tlento updated! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Engine failures abound. Looks like a snapshot update and some way of installing databricks to make them happy (editable install in the databricks env, I think) should do it.
e5874a2
to
86cb745
Compare
@tlento SORRY! Should be good now! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's goooooo! 🚀
3728559
to
d233a1d
Compare
Support for rendering
DATE_TRUNC
statements with sub-daily granularity options.Includes validation for engines that don't support certain granularities.
Note about validation: warehouse validations in YAML would be ideal, but we don't have those currently. Query parsing validations would also be ideal, but the query parse has no awareness of the engine being queried. This seemed like the next best option, and it's such an rare edge case that I'm not too concerned about optimizing this error.