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

Review 'default' retrieval algorithm #161

Open
renekrie opened this issue Jul 4, 2023 · 0 comments
Open

Review 'default' retrieval algorithm #161

renekrie opened this issue Jul 4, 2023 · 0 comments

Comments

@renekrie
Copy link
Contributor

renekrie commented Jul 4, 2023

Chorus let's the user choose from a list of pre-configured search algorithms that each yield different result sets and rankings.

The default algorithm is a pretty bad one that we would always de-recommend in e-commerce search, eg. using mm<100%. This is problematic from a number of perspectives:

  • As Chorus is meant to be an example application for a good e-commerce search, the default algorithm should be a reasonably good one
  • As we are adding vector search, we default increasingly serves as a reference for comparison, which would not make sense, if it is so bad that nobody would use it in practice. More concretely, we have a search algorithm that uses vectors for boosting but keywords for retrieval. Which algorithm would we compare it to? Should we turn on mm=100% for hybrid search? - In the context of telling the story - default vs. hybrid search - we should keep it off. But in a more general e-commerce search context, it doesn't make sense.
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

No branches or pull requests

1 participant