Description
When executing hybrid searches with relativeScoreFusion, documents without any bm25 score can be scored better than the last bm25 result which receives a score of 0 after normalization.
IMHO the documents retrieved only via vector search must be assigned a value of 0 for the bm25 part before applying the fusion, by doing that the last bm25 result will rank up as the normalized score won’t be zero.
Is that a bug or is it by design?
Server Setup Information
- Weaviate Server Version: 1.24.8
- Deployment: docker
- Multi Node? Number of Running Nodes: 1
- Client Language and Version: api directly
- Multitenancy?: no