For now, BM25 no longer implements MaxScore. The underlying issue with its implementation is still not fixed, but unless there's a need for better performance with this model, commenting it out is at least solution for the upcoming 3.8 release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The real issue here is that bm25 is a scoring operator, so it should only have one children, and be repeated for all its children. The low map we're seeing is because Galago hides the error and runs single term queries instead of the whole query!
This is a bug, and Galago ought to crash if it gets a bm25 node with multiple text children.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For now, BM25 no longer implements MaxScore. The underlying issue with its implementation is still not fixed, but unless there's a need for better performance with this model, commenting it out is at least solution for the upcoming 3.8 release.
The real issue here is that
bm25is a scoring operator, so it should only have one children, and be repeated for all its children. The low map we're seeing is because Galago hides the error and runs single term queries instead of the whole query!This is a bug, and Galago ought to crash if it gets a
bm25node with multiple text children.