Remove unnecessary joins for list node and task execution entities in flyteadmin db queries #5935
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.
Why are the changes needed?
for ListNodeExecutions and ListTaskExecutions queries we always force a join on executions, and for the latter, node executions. This is inefficient and unnecessary when we don't reference cross table entities in request filters.
Furthermore, this change updates how we query on execution identifier filters to avoid forcing an unnecessary join there too.
What changes were proposed in this pull request?
See description. This only forces joins when they are necessitated by the presence of request filters.
How was this patch tested?
Setup process
Tested with single binary and verified I could launch executions and interact with the console. I forced cross table joins with request filters and saw SQL logs reflect that.
Screenshots
Check all the applicable boxes
Related PRs
Docs link