-
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
Handle no-metric queries with sub-daily metric_time
#1359
Merged
courtneyholcomb
merged 9 commits into
court/test-time-spines
from
court/subd-no-metrics
Jul 30, 2024
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
1b4bdf7
Update invalid granularity assumptions
courtneyholcomb 1c772f1
Handle no-metric queries with sub-daily metric_time
courtneyholcomb 6df42d9
Changelog
courtneyholcomb 2c440f2
Add new test dimensions with sub-daily granularities
courtneyholcomb de20f4f
Determine if plan should be distinct_values from params
courtneyholcomb 16c999b
Add SQL rendering tests for no-metric queries
courtneyholcomb bf490d1
Add check query tests for no-metric queries
courtneyholcomb e984404
Update SQL engine snapshots
courtneyholcomb 763db74
Fix issue causing inconsistent ordering of specs in snapshots
courtneyholcomb File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
kind: Features | ||
body: Enable sub-daily queries without metrics. | ||
time: 2024-07-27T08:11:06.357653-07:00 | ||
custom: | ||
Author: courtneyholcomb | ||
Issue: "1359" |
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -101,7 +101,12 @@ def without_first_entity_link(self) -> TimeDimensionSpec: # noqa: D102 | |
|
||
@property | ||
def without_entity_links(self) -> TimeDimensionSpec: # noqa: D102 | ||
return TimeDimensionSpec.from_name(self.element_name) | ||
return TimeDimensionSpec( | ||
element_name=self.element_name, | ||
time_granularity=self.time_granularity, | ||
date_part=self.date_part, | ||
entity_links=(), | ||
Comment on lines
+105
to
+108
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 commentThe reason will be displayed to describe this comment to others. Learn more. Your PR comment gifs are always the best. |
||
) | ||
|
||
@staticmethod | ||
def from_name(name: str) -> TimeDimensionSpec: # noqa: D102 | ||
|
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
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 default is because the time_spine_sources automatically include the DAY granularity (via
TimeSpineSource.create_from_manifest()
) if no custom time spines are found, correct?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 default is set so that if you query ambiguous
metric_time
without metrics, we don't return nanoseconds if you have that time spine configured. Sincemetric_time
defaults toDAY
in all other scenarios (unless overridden by the metric's default granularity), this seemed like the expected behavior.