Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The API for NoSQL Async Java SDK differs from the API for NoSQL Java SDK by providing asynchronous operations with support for the Netty library. The pre-existing API for NoSQL Java SDK doesn't support asynchronous operations.
Important
This is not the latest Java SDK for Azure Cosmos DB! We strongly recommend using Azure Cosmos DB Java SDK v4 for your project. To upgrade, follow the instructions in the Migrate to Azure Cosmos DB Java SDK v4 guide and the Reactor vs RxJava guide.
Important
On August 31, 2024, Microsoft retired the Azure Cosmos DB Async Java SDK v2.x. Azure Cosmos DB no longer provides maintenance and support for this SDK. Follow the instructions provided earlier to migrate to Azure Cosmos DB Java SDK v4.
| Links | |
|---|---|
| Release Notes | Release notes for Async Java SDK |
| SDK Download | Maven |
| API documentation | Java API reference documentation |
| Contribute to SDK | GitHub |
| Get started | Get started with the Async Java SDK |
| Code sample | GitHub |
| Performance tips | GitHub readme |
| Minimum supported runtime | JDK 8 |
Release history
The Azure Cosmos DB Java SDK source repo maintains the release history. For a detailed list of feature releases and bugs fixed in each release, see the SDK changelog documentation.
FAQ
How will I be notified of the retiring SDK?
Microsoft provides 12 months' advance notice before the end of support for the retiring SDK to help you smoothly transition to a supported SDK. You receive notifications through these communication channels: the Azure portal, Azure updates, and direct communication to assigned service administrators.
Can I author applications by using a to-be-retired Azure Cosmos DB SDK during the 12-month period?
Yes, you can use the to-be-retired Azure Cosmos DB SDK to author, deploy, and modify applications during the 12-month notice period. We recommend that you migrate to a newer supported version of the Azure Cosmos DB SDK during the 12-month notice period, as appropriate.
After the retirement date, what happens to applications that use the unsupported Azure Cosmos DB SDK?
After the retirement date, Azure Cosmos DB no longer makes bug fixes, adds new features, or provides support for the retired SDK versions. If you choose not to upgrade, Azure Cosmos DB continues to serve requests sent from the retired versions of the SDK.
Which SDK versions will have the latest features and updates?
New features and updates are added only to the latest minor version of the latest supported major SDK version. We recommend that you always use the latest version to take advantage of new features, performance improvements, and bug fixes. If you're using an old, non-retired version of the SDK, your requests to Azure Cosmos DB still function, but you don't have access to any new capabilities.
What should I do if I can't update my application before a cutoff date?
We recommend that you upgrade to the latest SDK as early as possible. After an SDK is tagged for retirement, you have 12 months to update your application. If you're not able to update by the retirement date, Azure Cosmos DB continues to serve requests sent from the retired versions of the SDK, so your running applications continue to function. But Azure Cosmos DB no longer makes bug fixes, adds new features, or provides support for the retired SDK versions.
If you have a support plan and require technical support, contact us by filing a support ticket.
How can I request features be added to an SDK or connector?
New features aren't always added to every SDK or connector immediately. If there's a feature that isn't supported that you'd like added, add feedback to our community forum.