It's worth adding that Lucene's BlendedTermQuery, (used in Elasticsearch's
cross_field search), attempts to blend field's document frequency together.
So I wonder what BlendedTermQuery plus BM25 similarity per-field would do?
It might be close to true BM25F aside for the length issue.
(You'd have
Hi David,
It may not matter for your use case but just in case you really are
interested in the "real BM25F" there is a difference between configuring K1
and B for different fields in Solr and a "real" BM25F implementation. This
has to do with Solr's model of fields being mini-documents (i.e. ea
@lucene.apache.org
Subject: Solr Support for BM25F
Hello,
I am developing an enterprise search engine for a project and I was hoping to
implement BM25F ranking algorithm to configure the tuning parameters on a per
field basis. I understand BM25 similarity is now supported in Solr but I was
hoping to be able to
@lucene.apache.org At: Apr 14 2016 17:48:50
To: solr-user@lucene.apache.org
Subject: Re: Solr Support for BM25F
Hey David
You can configure BM25 differently for each field by configuring the
similarity per field type, as shown here in this example from the Solr tests
https://github.com/sudarshang
: a per field basis. I understand BM25 similarity is now supported in Solr
BM25 has been supported for a while, the major change recently is that it
is now the underlying default in Solr 6.
: but I was hoping to be able to configure k1 and b for different fields such
: as title, description, an
Hey David
You can configure BM25 differently for each field by configuring the
similarity per field type, as shown here in this example from the Solr tests
https://github.com/sudarshang/lucene-solr/blob/master/solr/core/src/test-files/solr/conf/schema-bm25.xml#L32
On Thu, Apr 14, 2016 at 12:41 P
Hello,
I am developing an enterprise search engine for a project and I was hoping
to implement BM25F ranking algorithm to configure the tuning parameters on
a per field basis. I understand BM25 similarity is now supported in Solr
but I was hoping to be able to configure k1 and b for different field
