-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Update core to support DSI 0.8.3 #10990
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #10990 +/- ##
==========================================
- Coverage 89.17% 89.13% -0.05%
==========================================
Files 183 183
Lines 23783 23784 +1
==========================================
- Hits 21209 21200 -9
- Misses 2574 2584 +10
Flags with carried forward coverage won't be shown. Click here to find out more.
|
5c443d7
to
890a1b0
Compare
890a1b0
to
0256834
Compare
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.
This looks good! I had one question about MFs/DSIs expectations on case. Depending on the answer to that, we might need to make changes, or we might just be good to go 🙂
def _get_optional_time_window( | ||
self, unparsed_window: Optional[str] | ||
) -> Optional[MetricTimeWindow]: | ||
if unparsed_window is not None: | ||
parts = unparsed_window.split(" ") | ||
parts = unparsed_window.lower().split(" ") |
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.
Does DSI/Metricflow require these be lowercase now? If so, this may be breaking as for already parsed manifests 🤔
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.
Nope! It should not be case sensitive. This is lowercasing it before we get it so that the user doesn't need to worry about lowercasing it but we can expect lowercase on our side. Will added tests for case sensitivity in DSI, too.
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 words that concern me are
but we can expect lowercase on our side
I'm not sure you can unfortunately, but I could be wrong about that. Could you point me to the tests around case sensitivity in DSI?
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.
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 me go back and make sure all other fields have this covered, too
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.
Alright @QMalcolm - sorry for the delay on this, had some other high prios and then didn't want to mess with code freeze! 🥶
We bumped the version of DSI one more time with some changes to fix the issues with case sensitivity. This is the PR with those changes, but these commits are most relevant: 1, 2.
Let us know if you think there are any other issues here! The thorough review was much appreciated 🙏
Once approved, we shouldn't merge quite yet - just because we want to coordinate the merge timing so that we will have time to update mantle between when this merges and the next sync to mantle.
cc @WilliamDee
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.
I think github screwed up those links somehow. They point to https://github.com/dbt-labs/dbt-core/pull/2083a249889252823b097098cb03471f2db0d00e and https://github.com/dbt-labs/dbt-core/pull/00abab69a8b4537abcc0ea9e544547e99a3c27a2. Which are commits, but on DSI, not core.
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.
For the public observer, the correct links are
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.
Looks good to me! Thank you for resolving the case sensitivity issue ❤️
…window, so removing tests that includes them otherwise
e0fcb99
to
363e44b
Compare
Problem
Upgrade to DSI 0.8.3 to support passing custom time grain in the yaml spec
schema change PR: dbt-labs/schemas.getdbt.com#70
Solution
Checklist