4.53.0 (2023-12-01)
Bugs Fixed
- Fixed a bug resulting in
CosmosDiagnosticsContext.getStatusCode()
always returning0
forreadMany
operations. - See PR 37394 - Fixed an issue where PartitionKeyRange request will not do cross region retry. - See PR 37403
- Fixed an issue where Session consistency was not honored when the consistency level on the
CosmosClientBuilder.consistencyLevel
was not explicitly set toConsistencyLevel.SESSION
but the default account consistency level is session. If not enforcing session consistency is the intended behavior, you can set theCosmsoClientBuilder.consistencyLevel
toConsistencyLevel.EVENTUAL
. - See PR 37377 - Fixed an issue where client level
EndToEndOperationLatencyPolicyConfig.availabilityStrategy
is not being applied forquery
- See PR 37511 - Fixed an issue where operation is not cancelled based on
CosmosEndToEndOperationLatencyPolicyConfig.endToEndOperationTimeout
when429
happens - See PR 37764 - Fixed an issue where
CosmosEndToEndOperationLatencyPolicyConfig.endToEndOperationTimeout
is not applied forReadMany
- See PR 37764 - Fixed an issue with OFFSET and LIMIT query clause returning partial query results when used with DISTINCT - See PR 37860
Other Changes
- Modified the event payload when diagnostic details are traced (vis Open telemetry traces). The diagnostics can exceed the max. attribute size of 8KB. This PR will split the diagnostics and trace them in multiple events (ordered by
SequenceNumber
attribute) to ensure the full diagnostics message is available in logged events. - See PR 37376 - Added
sessionRetryCfg
to the diagnostic string and modifiedproactiveInit
key name toproactiveInitCfg
in the diagnostic string. - See PR 36711 - Modified
429
retry backoff time whenretryAfter
is not being returned from server. For429/3200
, SDK will retry immediately, for others SDK will backoff 100ms - See PR 37764