DEVPROD-10179: Add task name and status filtering #8800
Conversation
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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
… DEVPROD-10179
… DEVPROD-10179
hadjri
reviewed
Mar 10, 2025
| versionLookupKey := "version" | ||
|
|
||
| // Get version documents | ||
| pipeline = append(pipeline, bson.M{ |
There was a problem hiding this comment.
Can we verify the performance of this pipeline against e.g. server or mms?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
DEVPROD-10179, DEVPROD-10180
Description
Add the ability to filter waterfall queries by task name or status. This query is run when a user applies a filter that results in
n < limitversions being shown as active on the page.Previous implementations of this (e.g. for the project health page) had iterated through versions attempting to find one whose tasks matched the criteria. Here, we instead find recent tasks from
limitunique versions that match the filters, and then look up the corresponding versions. Based on pipeline testing, performance seems acceptable since we only look at tasks within the 300 most recent versions. It's possible an index will further improve performance.Testing