3.52.1: Adds Patch release 3.52.1 #5293
Merged
microsoft-github-policy-service[bot] merged 3 commits intoreleases/3.52.1from Jul 17, 2025
Merged
3.52.1: Adds Patch release 3.52.1 #5293microsoft-github-policy-service[bot] merged 3 commits intoreleases/3.52.1from
microsoft-github-policy-service[bot] merged 3 commits intoreleases/3.52.1from
Conversation
Windows 365 Defender team faced an issue with their HPK container set
up. Problem was when they set the root level partition key in the
QueryRequestOptions and run a query they would get the data back when
running on windows but for other environments(like docker) they were
getting an exception
For Docker they were getting 410(Gone) exception
Microsoft.Azure.Cosmos.CosmosException : Response status code does not
indicate success: Gone (410); Substatus: 1002; ActivityId:
623305e2-9a69-4b65-aa9b-911ee8ac3533; Reason: (Epk Range:
[0DCEB8CE51C6BFE84F4BD9409F69B9BB,0DCEB8CE51C6BFE84F4BD9409F69B9BBFF) is
gone.);
The root of the problem was that for non-window(x64) environment we were
getting the query plan from gateway(unlike windows where we use the
ServiceInterop dll) and after we got the plan we funnel it through
RequestInvokerHandler pipeline. The pipeline has a check where it sees
that if a feedRange is provided and if it returns more than 1
overlapping ranges it throws a gone exception but in this particular
case this is a valid scenario(edge case).
e.g
datatable (MinEPK: string, MaxEPK: string, PKrangeId)
[
"0D4DC2CD8F49C65A8E0C5306B61B4343","0DCEB8CE51C6BFE84F4BD9409F69B9BB2164DEBD78C50C850E0C1E3E3F0579ED",0
"0DCEB8CE51C6BFE84F4BD9409F69B9BB2164DEBD78C50C850E0C1E3E3F0579ED","1080F600C27CF98DC13F8639E94E7676"
1
]
If our provided partition key results in a hash e.g
0DCEB8CE51C6BFE84F4BD9409F69B9BB that lies between the above 2 records,
we will get overlapping ranges back.
Fix:
Fix it to explicitly make a check and see if its a Query Plan , if it is
then allow it to progress.
Testing:
I was able to get access to the Defender Team DB where they were facing
this issue. I manually tested the following E2E use cases and got the
desired results.
On Windows -> with PartitionKey specified
Diagnostics is : {"Summary":{"DirectCalls":{"(449, 5350)":6,"(200,
0)":2},"GatewayCalls":{"(200, 0)":4,"(304, 0)":1}}
Count: 24025; Severity: Medium;
Count: 24114; Severity: Informational;
Count: 23; Severity: High;
On Non_windows - with PartitionKey specified(in the QueryRequestOptions)
Diagnostics is : {"Summary":{"DirectCalls":{"(449, 5350)":2,"(200,
0)":2},"GatewayCalls":{"(200, 0)":5,"(304, 0)":1,"(0, 0)":1}}
Count: 24025; Severity: Medium;
Count: 24114; Severity: Informational;
Count: 23; Severity: High;
On Windows - no QueryRequestOption specified
Diagnostics is : {"Summary":{"DirectCalls":{"(200,
0)":2},"GatewayCalls":{"(200, 0)":4,"(304, 0)":1}}
Count: 24025; Severity: Medium;
Count: 24114; Severity: Informational;
Count: 23; Severity: High;
On Non_windows - no QueryRequestOption specified
Diagnostics is : {"Summary":{"DirectCalls":{"(200,
0)":2},"GatewayCalls":{"(200, 0)":5,"(304, 0)":1}}
Count: 24025; Severity: Medium;
Count: 24114; Severity: Informational;
Count: 23; Severity: High;
Problem writing a new reliable E2E test in the pipeline is the set up
needed to return overlapping ranges and we don't have control over when
partition split happens.
Talked to Ananth on how he tested it and he worked with Elasticity team
to create the database in the desired state, we can do the same in the
pipeline but need to check if our database accounts/containers get
cleaned up by some background job in the future(will check with Nalu on
this one).
I also explored the PartitionKeyHashRangeSplitterAndMerger class but
that works only with in-memory container and doesn't follow the
RequestInvokerHandler pipeline flow.
for the time being I added a unit test which will avoid any regression
in the future.
closes #5220
#5220
---------
Co-authored-by: Kiran Kumar Kolli <kirankk@microsoft.com>
## Description This bumps the SDK GA version from 3.52.1 to 3.52.0 and preview version from 3.53.0-preview.0 to 3.53.0-preview.1 It is a patch upgrade to the previous release. **There are no contract changes** ## Type of change Please delete options that are not relevant. - [] Bug fix (non-breaking change which fixes an issue) - [] New feature (non-breaking change which adds functionality) - [] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [] This change requires a documentation update ## Closing issues To automatically close an issue: closes #IssueNumber
ananth7592
requested review from
FabianMeiswinkel,
Pilchie,
adityasa,
khdang,
kirankumarkolli,
kirillg,
neildsh and
sboshra
as code owners
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
ananth7592
changed the title
kirankumarkolli
previously approved these changes
Jul 16, 2025
…ests (#5274) This PR fixes the account properties parsing logic for failing PPAF tests Please delete options that are not relevant. - [x] Bug fix (non-breaking change which fixes an issue) To automatically close an issue: closes #IssueNumber
kirankumarkolli
approved these changes
Jul 17, 2025
microsoft-github-policy-service
Bot
merged commit 79a11bf
into
releases/3.52.1
27 checks passed
microsoft-github-policy-service
Bot
deleted the
ananth/patch-release-3.52.1
branch
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
4 participants
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.
Description
Includes the following commit in the patch version release besides the required file changes for version upgrade to 3.52.1
QueryPlan : Fixes 410 Gone Exception on non-x64 platforms #5257
Type of change
Please delete options that are not relevant.
Closing issues
To automatically close an issue: closes #IssueNumber