-
Notifications
You must be signed in to change notification settings - Fork 483
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
[BLOG] Optimizing Hybrid Search in OpenSearch #3454
Comments
tagging @krisfreedain who had the initial conversation about this blog post together with Eric |
@wrigleyDan - Thanks for filing a blog issue. I am the blog manager, and wanted to reach out and let you know that when you have a draft ready for review, you are welcome to include it here in markdown format or email via G-docs. My email is [email protected]. You can also find me on public Slack - Eric and I work together often. |
@pajuric - thanks for following up on this. I sent you the current draft via email. Looking forward to working on this together with you! |
@wrigleyDan - I just reviewed the draft and provided feedback. Next step is to implement the edits and open a blog PR including the content so I can get this through reviews. Thanks again. |
Describe the blog post
Hybrid search is hard:
There exists no “one size fits all” solution. The best configuration depends on a plethora of factors related to any given search application’s data, users, or domain.
With the hybrid search optimizer, a set of notebooks, OpenSearch users are empowered to find the best parameter set for their application and explore ways to dynamically predict how the best hybrid search query looks like individually per query.
The blog post should share the approach and also experimentation results that were achieved using the ESCI dataset.
Preliminary outline:
Expected Title
Optimizing Hybrid Search in OpenSearch
Authors Name
Daniel Wrigley
Authors Email
[email protected]
Target Draft Date
11/26/2024
Blog Post Category
technical, partners
Target Publication Date
12/10/2024
Additional Info
The text was updated successfully, but these errors were encountered: