-
Notifications
You must be signed in to change notification settings - Fork 61
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
I'm not able to see which branch is for latest version of V3 version (3.7.5) #379
Comments
@apescione - We really recommend using the latest Cosmos V4 SDK. v3 has not been maintained for a while now. It has many issues, which all of them have already been resolved on V4. I would strongly push for V4 migration, rather v3 update. |
Hi @kushagraThapar , |
@apescione - @apescione - regarding cosmos V3 SDK - this is the branch we use for hotfix releases - which are not being done any more. In case you want to look up for specific code piece or any implementation details - here it is - https://github.com/Azure/azure-sdk-for-java/tree/release/cosmos_v3 |
@apescione please take a look at https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-setup-rbac |
Hi @milismsft, @kushagraThapar, as you can see, I'm in the middle ground, I can't improve the old one, either migrate to the new one. But, it's different if I could create a pull request on this branch: Let me know if this approach can be fine for you. |
@apescione The Cosmos DB AAD feature will be GA very soon, couple months from now at most and the chances we will make any changes into the feature between now and GA are very slim. IMHO it's best to start by migrating your code to V4 version of the CosmosDB Java SDK, incorporate the AAD authentication and test your code to make sure everything works as expected. |
It's not a bug, but I'm not able to find out the branch where is the code for version 3.7.5 (latest https://mvnrepository.com/artifact/com.microsoft.azure/azure-cosmos/3.7.5)
I need to create a pull request to provide an enhancement for this library (already present on V4), because I cannot adopt the v4 at the moment in my project.
The text was updated successfully, but these errors were encountered: