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

Migrate your application to use the Azure Cosmos DB .NET SDK v3 #326

Open
tchekdy opened this issue Mar 22, 2024 · 4 comments
Open

Migrate your application to use the Azure Cosmos DB .NET SDK v3 #326

tchekdy opened this issue Mar 22, 2024 · 4 comments

Comments

@tchekdy
Copy link

tchekdy commented Mar 22, 2024

Version 2.x of the Azure Cosmos DB .NET SDK will be retired.

Update to version 3 of the Azure Cosmos DB .NET SDK by 31 August 2024

You're receiving this email because you've used version 2.x of the Azure Cosmos DB .NET SDK.

On 31 August 2024 we'll retire version 2.x of the Azure Cosmos DB .NET SDK, and you'll need to update your SDK to version 3.x by that date. Version 3 of the Azure Cosmos DB .NET SDK includes many usability and performance improvements over version 2 of the SDK as well as access to new Azure Cosmos DB features.

Version 3 includes:

  • Improved performance through stream API support.
  • Built-in support for change feed processor library and bulk operations.
  • Mockable APIs for easier unit testing.
  • Improved diagnostics and observability experience.
  • Access to new APIs and features including transactional batch, patch, hierarchial partition keys and many more.

Required action

To avoid service disruptions, migrate to Azure Cosmos DB .NET SDK version 3 by 31 August 2024.

Untitled picture

@tchekdy
Copy link
Author

tchekdy commented Apr 3, 2024

Any update on this issue?

@tchekdy
Copy link
Author

tchekdy commented Apr 22, 2024

Hi Team,

Any update on this issue?
Thank you in advance.

@mlacey-dig
Copy link

I would love to know if there's any plans to release an updated version! I dont think I'd be able to personally figure out the migrations required to update the bot and would likely have to shut it off otherwise.

@Stefansof88
Copy link

Hey there, I just dropped Icebreaker in our org after a month of testing and got this message :) So yes, we need some help from these clever folks :)

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

No branches or pull requests

3 participants