Skip to content
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

maxVectorDistance support #198

Open
databyjp opened this issue Sep 20, 2024 · 4 comments · May be fixed by #245
Open

maxVectorDistance support #198

databyjp opened this issue Sep 20, 2024 · 4 comments · May be fixed by #245

Comments

@databyjp
Copy link
Collaborator

The TS client does not yet seem to have support for the recently added maxVectorDistance hybrid search parameter.

Weaviate DB PR: weaviate/weaviate#5643

@michael-pont
Copy link

I would also be interested in this as I am implementing hybrid search with move to and move away. I've seen that maxVectorDistance helps with returning more relevant results especially with ranked fusion enabled.

@tsmith023
Copy link
Contributor

I will be shipping this later this week in v3.3.2 @michael-pont 😁

@tsmith023 tsmith023 linked a pull request Jan 6, 2025 that will close this issue
@michael-pont
Copy link

Awesome, thanks 👍 I'm testing out the vector search params move to and move away right now. Do you happen to know what the force params mean? I've played around with it and it seems like it's a reward / penalty but the documentation in hybrid search doesn't explain it in detail

@databyjp
Copy link
Collaborator Author

databyjp commented Jan 7, 2025

Hi @michael-pont yes. It's exactly as you mentioned - a weighting to be applied.

It's documented here, sorry about that.
https://weaviate.io/developers/weaviate/api/graphql/search-operators#neartext

I will work on adding the info to the concepts page here:
https://weaviate.io/developers/weaviate/concepts/search/vector-search

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 a pull request may close this issue.

3 participants