Skip to content
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

[Cosmos DB] Release 4.5.0 #884

Merged
merged 4 commits into from
Feb 12, 2024
Merged

[Cosmos DB] Release 4.5.0 #884

merged 4 commits into from
Feb 12, 2024

Conversation

ealsur
Copy link
Member

@ealsur ealsur commented Feb 9, 2024

This PR prepares the 4.5.0 release which includes

  1. Bumping the SDK to 3.38.1
  2. Applying a temporary fix to Scale Controller Metrics APIs. When the Scale Controller runs and the customer Function instances are dormant, there is a chance that the monitored container splits. In this case, the Metrics API is throwing a CosmosException with StatusCode 410. The solution is to return a Metric value that would prompt the Scale Controller to at least start 1 instance, which will take care of handling the split.

Bumping to SDK to 3.38.1 includes related fixes to the Extension:

  • 4220 Change Feed Processor: Fixes disposal of unused CancellationTokenSource (#4220)
  • 4276 Change Feed Processor: Fixes LeaseLostException on Notifications API for Renewer (#4276)
  • 4251 Emulator : Adds support for flag in connection string to ignore SSL check (#4251)

Along other general improvements: https://raw.githubusercontent.com/Azure/azure-cosmos-dotnet-v3/master/changelog.md

Closes #762

@ealsur ealsur merged commit 7e39fae into dev Feb 12, 2024
7 checks passed
@ealsur ealsur deleted the users/ealsur/sdkbump3381 branch February 12, 2024 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cosmos DB trigger is not connecting to CosmosDB Emulator
2 participants