-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[FEATURE REQ] Azure Cosmos SDK can not work with Spring Boot 3.0.0-M3 #29979
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kushagraThapar, @TheovanKraay |
is there any tool to check if any deprecated API is used? @joshfree maybe we can enable that check by default for the whole repo |
@stliu - I believe there are already tools setup for this and provide warnings on usage of deprecated APIs. @lmolkova 's PR fixes this issue. @lmolkova can you please close this github issue once your PR is merged. Thanks! |
@lmolkova - can we please close this issue if its done? |
I think I fixed it with #29990, @moarychan can you please try and see if it still reproduces? thanks! |
Fixed, thanks~ |
Is your feature request related to a problem? Please describe.
The latest Azure Cosmos SDK (
com.azure:azure-cosmos:4:32:1
) can work with Spring Boot 2.7.x, it's not compatible with the milestone version 3.0.0-M3, which the Spring will release its official version soon.Since Azure Cosmos uses a
reactor-core: 3.4.19
method that has been marked deprecated (reactor.core.publisher.Mono#subscriberContext(reactor.util.context.Context
)), the reactor core version managed in Spring Boot 3 Will be upgraded to3.5.0.M2
, this method has been removed in this version. I found this classRntbdTransportClient.java
using this method.Describe the solution you'd like
Use a new method instead of
Mono#subscriberContext(reactor.util.context.Context)
and release a new version for Spring Boot 3 users.Additional context
You can use this demo project to reproduce the below exception message:
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: