expose number of evaluated query plan options #6765
Merged
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
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: d96c609c34403a9f43c23874 |
|
@dariuszkuc, please consider creating a changeset entry in |
fc0fbbd to
a32576c
Compare
TylerBloom
reviewed
Feb 11, 2025
| @@ -296,6 +296,8 @@ pub enum SingleFederationError { | |||
| InterfaceKeyMissingImplementationType { message: String }, | |||
| #[error("@defer is not supported on subscriptions")] | |||
| DeferredSubscriptionUnsupported, | |||
| #[error("{message}")] | |||
| QueryPlanComplexityExceeded { message: String }, | |||
sachindshinde
requested changes
Feb 11, 2025
lrlna
reviewed
Feb 11, 2025
|
@lrlna new metric is added to the |
lrlna
reviewed
Feb 11, 2025
TylerBloom
approved these changes
Feb 11, 2025
sachindshinde
approved these changes
Feb 11, 2025
duckki
reviewed
Feb 11, 2025
Before we start generating a query plan, we need to first evaluate all possible ways (options) that given query can be resolved. This PR exposes number of options that were considered to generate a final query plan.
Co-authored-by: Iryna Shestak <shestak.irina@gmail.com>
1af8bdf to
9eb047f
Compare
|
@mergify backport 1.x |
✅ Backports have been created
|
mergify bot
pushed a commit
that referenced
this pull request
Feb 11, 2025
Before we start generating a query plan, we need to first evaluate all possible ways (options) that given query can be resolved. This PR exposes number of options that were considered to generate a final query plan. (cherry picked from commit 4fe75e8)
dariuszkuc
added a commit
that referenced
this pull request
Feb 11, 2025
Before we start generating a query plan, we need to first evaluate all possible ways (options) that given query can be resolved. This PR exposes number of options that were considered to generate a final query plan. Co-authored-by: Dariusz Kuc <9501705+dariuszkuc@users.noreply.github.com>
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.
Before we start generating a query plan, we need to first evaluate all possible ways (options) that given query can be resolved. This PR exposes number of options that were considered to generate a final query plan.