Skip to content
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

Select appropriate time spine node for metric_time queries without metrics #1407

Merged
merged 1 commit into from
Sep 24, 2024

Conversation

courtneyholcomb
Copy link
Contributor

There are very few cases where multiple source nodes can satisfy the same linkable spec, but one instance in which that is the case is when metric_time is queried without metrics. In that case, we will use a time spine node to satisfy metric_time. Previously, we were choosing the time spine nodes that could support the selected grain, and then narrowing down to the one with the fewest satisfiable linkable specs. This logic was working because, before custom granularities, the time spine with the fewest satisfiable linkable specs was always the time spine with the largest compatible base granularity. With the addition of custom granularities, though, the time spine with the largest compatible base granularity might have any number of satisfiable linkable specs. This changes updates the source node selection logic to choose the time spine with the largest compatible base granularity, regardless of the number of satisfiable linkable specs.

@cla-bot cla-bot bot added the cla:yes label Sep 19, 2024
Copy link
Contributor

@tlento tlento left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@courtneyholcomb courtneyholcomb merged commit eb6509f into main Sep 24, 2024
25 checks passed
@courtneyholcomb courtneyholcomb deleted the court/time-spine-select branch September 24, 2024 03:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants