-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fixing issues with returning a Flux<JsonNode> in reactive spring. #33730
Conversation
API change check API changes are not detected in this pull request. |
/azp run java - cosmos - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hi All , is this fix released to PROD ? we want to start using the latest cosmos version |
not yet, it will go into the next release, current ETA by the end of this week. You can use use this link for tracking: https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-spring-data-cosmos/CHANGELOG.md |
Hi All, can someone confirm if the fix is live ? |
@abhitwr - yes, this was released in 3.33.0. |
Description
Issues were introduced with annotated queries and returning Flux from Reactive Spring. Updating the ReactiveCosmosTemplate to have the same behavior as CosmosTempalte.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines