Use cancellation token in DbCommand.ExecuteReaderAsync call in DAB layer #3300
Merged
anushakolan merged 16 commits intomainfrom Mar 30, 2026
Merged
Use cancellation token in DbCommand.ExecuteReaderAsync call in DAB layer #3300anushakolan merged 16 commits intomainfrom
anushakolan merged 16 commits intomainfrom
Conversation
…execution https://dev.azure.com/powerbi/AppDev/_workitems/edit/2004135 RequestTimeoutAttribute won’t take effect during query execution Problem: RequestTimeoutAttribute only works during graphql workload execution, it doesn’t take effect during query execution due to request executor does NOT implement cancellation token logic. Fix: pass cancellation token to DAB layer to DbCommand.ExecuteReaderAsync call
naxing123
requested review from
Alekhya-Polavarapu,
JerryNixon,
RubenCerna2079,
aaronburtle,
anushakolan,
rusamant,
sourabh1007,
souvikghosh04,
stuartpa and
vadeveka
as code owners
naxing123
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
This PR ensures GraphQL request cancellations/timeouts propagate into the DAB database execution by passing HttpContext.RequestAborted into DbCommand.ExecuteReaderAsync, and adds unit tests to validate cancellation behavior with the Polly retry policy.
Changes:
- Pass
CancellationTokenintoDbCommand.ExecuteReaderAsync(CommandBehavior, CancellationToken)in the DAB query execution path. - Add unit tests covering cancellation/timeout exceptions and ensuring retries are not attempted.
- Add a unit test asserting DB execution time is recorded even when an exception occurs during execution.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| src/Core/Resolvers/QueryExecutor.cs | Passes HttpContext.RequestAborted into ExecuteReaderAsync while consolidating CommandBehavior selection. |
| src/Service.Tests/UnitTests/SqlQueryExecutorUnitTests.cs | Adds multiple unit tests around cancellation propagation and non-retry behavior. |
Aniruddh25
reviewed
Mar 19, 2026
Aniruddh25
reviewed
Mar 19, 2026
Aniruddh25
requested changes
Mar 19, 2026
Collaborator
Aniruddh25
left a comment
Aniruddh25
left a comment
There was a problem hiding this comment.
Needs some test deduplication.
1) merged two tests 2) updated the queryExecutor contrtructor parameter after merging main
Aniruddh25
approved these changes
Mar 21, 2026
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
Aniruddh25
approved these changes
Mar 24, 2026
anushakolan
reviewed
Mar 24, 2026
anushakolan
requested changes
Mar 24, 2026
Contributor
anushakolan
left a comment
anushakolan
left a comment
There was a problem hiding this comment.
The one comment from copilot is valid, and it is a better way to verify that there was no retry. Please address that, rest LGTM!
vadeveka
approved these changes
Mar 26, 2026
vadeveka
approved these changes
Mar 27, 2026
anushakolan
approved these changes
Mar 30, 2026
Contributor
|
LGTM! |
naxing123
added a commit
that referenced
this pull request
Apr 1, 2026
…yer (#3300) This is to address #3301 Use cancellation token in DbCommand.ExecuteReaderAsync call in DAB layer Problem: RequestTimeoutAttribute only works during graphql workload execution, it doesn’t take effect during query execution as the logic to use cancellation token to DAB layer is NOT implemented, even though the code to pass cancellation token to DAB is already implemented. Fix: Use cancellation token to DAB layer in DbCommand.ExecuteReaderAsync call ## Why make this change? - This is the 3rd task to address multiple GraphQL timeout related issues. Discussion: https://microsoft.sharepoint.com/:w:/r/teams/dbsaaspillar/_layouts/15/doc2.aspx?sourcedoc=%7B230dcf09-f556-4071-877a-8294b7df7338%7D&action=edit&wdPid=62b0c291&share=IQEJzw0jVvVxQId6gpS333M4AS2c9wqqYSgUlkTBDxQSCEw ## What is this change? - Summary of how your changes work to give reviewers context of your intent. - Use cancellation token(if any) in DbCommand.ExecuteReaderAsync call in DAB layer ## How was this tested? - [ ] Integration Tests - [X] Unit Tests - Also did manual test with long running(3 minutes) SQL query from graphql and cancellation token with 30 seconds timeout, from debugger I can see code goes to DbCommand.ExecuteReaderAsync call in DAB layer and times out after 30 seconds. --------- Co-authored-by: Aniruddh Munde <[email protected]> Co-authored-by: Anusha Kolan <[email protected]>
naxing123
added a commit
that referenced
this pull request
Apr 2, 2026
…yer (#3300) This is to address #3301 Use cancellation token in DbCommand.ExecuteReaderAsync call in DAB layer Problem: RequestTimeoutAttribute only works during graphql workload execution, it doesn’t take effect during query execution as the logic to use cancellation token to DAB layer is NOT implemented, even though the code to pass cancellation token to DAB is already implemented. Fix: Use cancellation token to DAB layer in DbCommand.ExecuteReaderAsync call ## Why make this change? - This is the 3rd task to address multiple GraphQL timeout related issues. Discussion: https://microsoft.sharepoint.com/:w:/r/teams/dbsaaspillar/_layouts/15/doc2.aspx?sourcedoc=%7B230dcf09-f556-4071-877a-8294b7df7338%7D&action=edit&wdPid=62b0c291&share=IQEJzw0jVvVxQId6gpS333M4AS2c9wqqYSgUlkTBDxQSCEw ## What is this change? - Summary of how your changes work to give reviewers context of your intent. - Use cancellation token(if any) in DbCommand.ExecuteReaderAsync call in DAB layer ## How was this tested? - [ ] Integration Tests - [X] Unit Tests - Also did manual test with long running(3 minutes) SQL query from graphql and cancellation token with 30 seconds timeout, from debugger I can see code goes to DbCommand.ExecuteReaderAsync call in DAB layer and times out after 30 seconds. --------- Co-authored-by: Aniruddh Munde <[email protected]> Co-authored-by: Anusha Kolan <[email protected]>
naxing123
added a commit
that referenced
this pull request
Apr 2, 2026
…sync call in DAB layer (#3406) ## Why make this change? This backport fix for to address GraphQL timeout related issues. ## What is this change? Cherry-picked PR: Use cancellation token in DbCommand.ExecuteReaderAsync call in DAB layer #3300 ## How was this tested? 1. Existing and newly added tests in the source PR. 2. Also did manual test with long running(3 minutes) SQL query from graphql and cancellation token with 30 seconds timeout, from debugger I can see code goes to DbCommand.ExecuteReaderAsync call in DAB layer and times out after 30 seconds. ## Sample Request(s) N/A --------- Co-authored-by: Aniruddh Munde <[email protected]> Co-authored-by: Anusha Kolan <[email protected]>
This file contains hidden or 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
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.
This is to address #3301
Use cancellation token in DbCommand.ExecuteReaderAsync call in DAB layer
Problem:
RequestTimeoutAttribute only works during graphql workload execution, it doesn’t take effect during query execution as the logic to use cancellation token to DAB layer is NOT implemented, even though the code to pass cancellation token to DAB is already implemented.
Fix:
Use cancellation token to DAB layer in DbCommand.ExecuteReaderAsync call
Why make this change?
What is this change?
How was this tested?