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

[DOC] Incorrect Hybrid Search Documentation #7401

Closed
1 of 4 tasks
navneet1v opened this issue Jun 17, 2024 · 0 comments · Fixed by #7511
Closed
1 of 4 tasks

[DOC] Incorrect Hybrid Search Documentation #7401

navneet1v opened this issue Jun 17, 2024 · 0 comments · Fixed by #7511
Assignees
Labels
2 - In progress Issue/PR: The issue or PR is in progress.

Comments

@navneet1v
Copy link
Contributor

navneet1v commented Jun 17, 2024

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
In the documentation of hybrid search it is mentioned this Before using a hybrid query, you must set up a machine learning (ML) model

ReF: https://opensearch.org/docs/latest/query-dsl/compound/hybrid/#:~:text=Before%20using%20a%20hybrid%20query%2C%20you%20must%20set%20up%20a%20machine%20learning%20(ML)%20model

Same thing is mentioned here: https://opensearch.org/docs/latest/search-plugins/hybrid-search/#using-hybrid-search:~:text=Before%20using%20hybrid%20search%2C%20you%20must%20set%20up%20a%20text%20embedding%20model.%20For%20more%20information%2C%20see%20Choosing%20a%20model.

This is completely incorrect. We should say that before following the below tutorial you should setup the model but setting of model is not a pre-requistic for using hybrid search

This is not correct. Setting of model is not required as hybrid search works with normal vector also. Due to this there has been a lot of confusion from customers that hybrid search requires ML model. This needs to be fixed.

What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
NA

@hdhalter hdhalter added 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. and removed untriaged labels Jun 24, 2024
@hdhalter hdhalter added 2 - In progress Issue/PR: The issue or PR is in progress. and removed 1 - Backlog - DEV Developer assigned to issue is responsible for creating PR. labels Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 - In progress Issue/PR: The issue or PR is in progress.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants