If you read the two jira issues, you'll discover that the BM25f that you point is buggy.
You should read the lucene flexscore branch (GSOC) at the top of lucene trunk
I started updating ES to lucene flexscore trunk, but I stopped for lack of time.
The index format in lucene trunk often changes, so it's not safe for production
Sent from my iPhone
On 03/mag/2011, at 02:59, conor firstname.lastname@example.org wrote:
Thanks for the pointers Otis.
I understand the underlying Lucene dependency. This link I mentioned
(http://nlp.uned.es/~jperezi/Lucene-BM25/) refers to an implementation of
BM25(F) on top of Lucene. It provides a number of extensions to Lucene for
Scorer, Query, Weight, and Similarity.
I think my question is better stated: supposing one had extensions for
Lucene that implemented BM25(F), how would they be passed through to Elastic
It seems like the main elements from the API (dsl) are there in terms of
field level boosting (so we could have a weighted sum of field level
rankings). But there would have to be a way to load the Lucene extensions.
If anyone can shed light on the path to pursue this, or if it has already
been done, I would be much obliged.
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/What-is-the-path-to-utilize-BM25F-with-Elastic-Search-tp2889935p2892048.html
Sent from the ElasticSearch Users mailing list archive at Nabble.com.