Skip to content

[release/9.0-staging] Bump version of Cosmos SDK from 3.45 to 3.48 to improve hybrid search experience out of the box #35946

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

Closed
wants to merge 1 commit into from

Conversation

maumar
Copy link
Contributor

@maumar maumar commented Apr 14, 2025

closing this in favor of PR directly against release/9.0 (rather than staging):
#35954


bumping cosmos sdk version to improve hybrid search experience out of the box - this is a dry run, will incorporate these changes to the proper 9.0 PR once/if we have green light for the bump

Continuation of #35909

Description
As part of adding full text search support we realized that some scenarios (specifically hybrid search and some instances of ContainsAll) don't work with the Cosmos SDK that is currently referenced by EFCore.Cosmos 9.x package. The issues can be solved by bumping SDK version to 3.48

Customer impact
Customers trying full text search will experience errors for some scenarios - cryptic exception (Syntax error near '-' for hybrid, and invalid results for some ContainsAll queries). Workaround is to manually upgrade Cosmos SDK dependency.

How found
Internal testing by the partner team.

Regression
No

Testing
All current Cosmos tests pass. Performed smoke test to validate that breaking change added in the SDK (requiring explicit Newtonsoft.Json dependency) doesn't have impact on the customer app.

Risk
Low. This can only affect customers using EFCore.Cosmos, one breaking change introduced in the SDK is benign from the perspective of customers using EFCore to communicate with Cosmos (EFCore package absorbs the breaking change).

@maumar maumar changed the base branch from main to release/9.0-staging April 14, 2025 01:26
@maumar maumar requested a review from AndriySvyryd April 14, 2025 01:28
Copy link
Member

@AndriySvyryd AndriySvyryd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@maumar maumar force-pushed the cosmos_fts_90_version_bump branch from 2c75d21 to cec0ba0 Compare April 14, 2025 23:28
@maumar maumar marked this pull request as ready for review April 14, 2025 23:28
@maumar maumar changed the title Cosmos fts 90 version bump [release/9.0-staging] Cosmos fts 90 version bump Apr 14, 2025
…rch experience

Continuation of #35909

Bumping version of Cosmos SDK improves user experience out of the box for some scenarios (namely hybrid search). Separated this from the main PR as it required separate approval.
@maumar maumar force-pushed the cosmos_fts_90_version_bump branch from cec0ba0 to dc84360 Compare April 14, 2025 23:38
@maumar maumar changed the title [release/9.0-staging] Cosmos fts 90 version bump [release/9.0-staging] Bump version of Cosmos SDK from 3.45 to 3.48 to improve full text search experience Apr 14, 2025
@maumar maumar added this to the 9.0.5 milestone Apr 15, 2025
@maumar maumar changed the title [release/9.0-staging] Bump version of Cosmos SDK from 3.45 to 3.48 to improve full text search experience [release/9.0-staging] Bump version of Cosmos SDK from 3.45 to 3.48 to improve hybrid search experience out of the box Apr 15, 2025
@maumar
Copy link
Contributor Author

maumar commented Apr 15, 2025

closing this in favor of PR directly against release/9.0 (rather than staging): #35954

@maumar maumar closed this Apr 15, 2025
@maumar maumar removed this from the 9.0.5 milestone Apr 15, 2025
@roji
Copy link
Member

roji commented Apr 15, 2025

closing this in favor of PR directly against release/9.0 (rather than staging)

FYI can also change the targeted branch (edit button on top) instead of opening a new PR.

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

Successfully merging this pull request may close these issues.

3 participants