-
Notifications
You must be signed in to change notification settings - Fork 254
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
inefficient query plans when using @context #3140
Merged
Merged
Changes from 3 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
ff5e2fa
Query plans that incorporated contextual variables could be inefficie…
clenfest 9888268
Argument naming was incorrect because it was occurring inside of loop…
clenfest 2ec181e
add changeset
clenfest f473842
get rid of whitespace only changes
clenfest f117c6d
Merge branch 'main' into clenfest/zzz
clenfest fcf48af
prettier and cspell fix
clenfest 8b14505
Merge branch 'main' into clenfest/zzz
clenfest df44700
Merge branch 'main' into clenfest/zzz
clenfest ab3dfcf
Merge branch 'main' into clenfest/zzz
clenfest 27b5860
basic requires test
clenfest 310b23d
Merge branch 'main' into clenfest/zzz
clenfest 0997fb7
simplifying handleRequires
clenfest b92e52f
refactoring
clenfest efce70b
Adjust calling code for split handleRequires(), paired with @clenfest
sachindshinde ff59e97
Merge remote-tracking branch 'upstream/main' into clenfest/zzz
sachindshinde 4f584d0
Revert unintended test changes from before
sachindshinde a04979f
add .gitleaksignore file
clenfest 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 @@ | ||
--- | ||
"@apollo/query-planner": patch | ||
"@apollo/query-graphs": patch | ||
--- | ||
|
||
Fixes edge case where contextual arguments can yield inefficient query plans. Also fixes naming of query plan arguments which can be a problem when using contextual variables in multiple subgraphs |
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.
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.
previously this was calculated in a single loop above -> any reason to move it down here? I think we only need the
builder.setContextMaps(...)
outside of the loop?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.
Yeah, it's like that because we only need to do the calculations once at the end. The fact that it was inside the loop was causing naming colisions.