-
Notifications
You must be signed in to change notification settings - Fork 495
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
Diagnostics : Adds Continuation Token from PkRange cache #3180
Conversation
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.
Please follow the required format: "[Internal] Category: (Adds|Fixes|Refactors|Removes) Description"
Internal should be used for PRs that have no customer impact. This flag is used to help generate the changelog to know which PRs should be included. Examples:
Diagnostics: Adds GetElapsedClientLatency to CosmosDiagnostics
PartitionKey: Fixes null reference when using default(PartitionKey)
[v4] Client Encryption: Refactors code to external project
[Internal] Query: Adds code generator for CosmosNumbers for easy additions in the future.
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.
Please follow the required format: "[Internal] Category: (Adds|Fixes|Refactors|Removes) Description"
Internal should be used for PRs that have no customer impact. This flag is used to help generate the changelog to know which PRs should be included. Examples:
Diagnostics: Adds GetElapsedClientLatency to CosmosDiagnostics
PartitionKey: Fixes null reference when using default(PartitionKey)
[v4] Client Encryption: Refactors code to external project
[Internal] Query: Adds code generator for CosmosNumbers for easy additions in the future.
Microsoft.Azure.Cosmos/src/Tracing/TraceData/ClientSideRequestStatisticsTraceDatum.cs
Outdated
Show resolved
Hide resolved
Title says "Cancellation Token" is it supposed to be "ContinuationToken"? |
What's the scenario for continuation token? (Is it for PkRangeFeed Api's) |
It is always ContinuationToken only..Sorry for the typo and confusion. |
Yes..it is the same..I have put link of the issue in the PR description for more detail. |
f411bef
to
1dfc08d
Compare
Microsoft.Azure.Cosmos/src/Tracing/TraceData/ClientSideRequestStatisticsTraceDatum.cs
Outdated
Show resolved
Hide resolved
1dfc08d
to
9f3fe57
Compare
0e3010f
to
5df4038
Compare
8819fad
to
5651586
Compare
...osoft.Azure.Cosmos/tests/Microsoft.Azure.Cosmos.EmulatorTests/CosmosItemSessionTokenTests.cs
Outdated
Show resolved
Hide resolved
{ | ||
this.jsonWriter.WriteObjectStart(); | ||
|
||
this.jsonWriter.WriteFieldName("Previous Continuation Token"); |
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.
Should we use "PreviousContinuationToken"? similar as "BELatencyInMs", no space in between
Description
After this PR,
Right now,
NoOpTrace
has been passed in most of the cases forPartitionKeyRangeCache
call. In future PRs, we will be removing NoOpTrace from these calls to get the proper diagnostics.Type of change
Closing issues
To automatically close an issue: closes #3167