-
Notifications
You must be signed in to change notification settings - Fork 43
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
Explain Request - Execution #326
Labels
Milestone
Comments
shahzadlone
changed the title
Explain Query - Execution
Explain Query - Execution (JSON)
Apr 19, 2022
shahzadlone
changed the title
Explain Query - Execution (JSON)
Explain Request - Execution (JSON)
Apr 26, 2022
Blocked by #521 |
4 tasks
Also blocked by the initial setup of metrics #293 |
Technically can be worked on after #970 is in.
|
shahzadlone
changed the title
Explain Request - Execution (JSON)
Explain Request - Execution
Mar 23, 2023
4 tasks
shahzadlone
added a commit
that referenced
this issue
Apr 1, 2023
- Resolves #326 - Description: Adds ability to return datapoints / information gathered at every planner step. The information is stored during execution, and gathered post execution. - Usage: Add `@explain(type: execute) ` after the `query` or `mutation` operation. - Execute explain request for `query` operation - example: ``` query @Explain(type: execute) { Address(groupBy: [country]) { country _group { city } } } ``` - Execute explain request for `mutation` operation - example: ``` mutation @Explain(type: execute) { update_address( ids: ["bae-c8448e47-6cd1-571f-90bd-364acb80da7b"], data: "{\"country\": \"USA\"}" ) { country city } } ```
shahzadlone
added a commit
that referenced
this issue
Apr 13, 2023
- Resolves #326 - Description: Adds ability to return datapoints / information gathered at every planner step. The information is stored during execution, and gathered post execution. - Usage: Add `@explain(type: execute) ` after the `query` or `mutation` operation. - Execute explain request for `query` operation - example: ``` query @Explain(type: execute) { Address(groupBy: [country]) { country _group { city } } } ``` - Execute explain request for `mutation` operation - example: ``` mutation @Explain(type: execute) { update_address( ids: ["bae-c8448e47-6cd1-571f-90bd-364acb80da7b"], data: "{\"country\": \"USA\"}" ) { country city } } ```
shahzadlone
added a commit
to shahzadlone/defradb
that referenced
this issue
Feb 23, 2024
- Resolves sourcenetwork#326 - Description: Adds ability to return datapoints / information gathered at every planner step. The information is stored during execution, and gathered post execution. - Usage: Add `@explain(type: execute) ` after the `query` or `mutation` operation. - Execute explain request for `query` operation - example: ``` query @Explain(type: execute) { Address(groupBy: [country]) { country _group { city } } } ``` - Execute explain request for `mutation` operation - example: ``` mutation @Explain(type: execute) { update_address( ids: ["bae-c8448e47-6cd1-571f-90bd-364acb80da7b"], data: "{\"country\": \"USA\"}" ) { country city } } ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sub Task of #35
Spec: https://source.getoutline.com/doc/explain-queries-jtaGX0L995
The text was updated successfully, but these errors were encountered: