wrote:
> Hi,
>
> I'm working on a Solr core where we don't want to use TF-IDF (BM25).
> We rank documents with boost based on popularity, exact match, phrase
> match,
> etc.
>
> To bypass TF-IDF, we use constant score like this "q=harry^=0.5
> potter^=0.
Hi,
I'm working on a Solr core where we don't want to use TF-IDF (BM25).
We rank documents with boost based on popularity, exact match, phrase match,
etc.
To bypass TF-IDF, we use constant score like this "q=harry^=0.5 potter^=0.5"
(score is always 1 before boost)
We have ju
On 10/17/2018 5:06 PM, Vincenzo D'Amore wrote:
I tried to use constant score into qf parameter but I had an exception.
Is this normal? The qf parameter actually is something like this:
field1^3 field2^4 field3^5... etc.
You didn't actually say, but it sounds like you're trying
Hi all,
I tried to use constant score into qf parameter but I had an exception.
Is this normal? The qf parameter actually is something like this:
field1^3 field2^4 field3^5... etc.
Because it's a query for an ecommerce website I don't want that the results
are influenced by tf/idf.
I call the mlt handler using a query which searches for a certain document
(?q=id:some_document_id). The reference document is included in the result and
the score is also returned. I found out, that the score if fixed, independent
of the document. So for each document id I get the same score. T
I am using the function query as part of an frange.
So, something like this: q=productId:[* TO *] fq={!frange
l=1}ceil(query(!v='documentType:(blah1 blah2 blah3)'))
This is actually quite slow. I suspect that the problem is the query
function is calculating a score for every document in the inde
On Oct 25, 2009, at 2:36 PM, Chris Hostetter wrote:
: Fair enough, I guess I was just kind of expecting a constant score
query + a
: function query to result in a score of whatever the function query
is. This
: is a common trick to sort by a function, but it's easy enough to
ju
: Fair enough, I guess I was just kind of expecting a constant score query + a
: function query to result in a score of whatever the function query is. This
: is a common trick to sort by a function, but it's easy enough to just ^0 the
: non function clause.
I think the root of hte iss
On Oct 22, 2009, at 9:44 PM, Chris Hostetter wrote:
: > Why wouldn't you just query the function directly and leave out
the *:* ?
:
: *:* was just a quick example, I might have other constant score
queries, but I
: guess I probably could do a filter query plus the function quer
: > Why wouldn't you just query the function directly and leave out the *:* ?
:
: *:* was just a quick example, I might have other constant score queries, but I
: guess I probably could do a filter query plus the function query, too.
I guess i don't udnerstand what your poin
wouldn't you just query the function directly and leave out the
*:* ?
*:* was just a quick example, I might have other constant score
queries, but I guess I probably could do a filter query plus the
function query, too.
: As a workaround, I can do: *:*^0 _val_:price_f, which gets rid of the query
: norm factor.
:
: I realize I could override the similarity or use the workaround, but I was
: just curious about what other people think of this.
Why wouldn't you just query the function directly and leave out the *:*
I have a simple set of docs containing two fields, an id and a price.
When I run a constant score query, such as *:*, I, of course, get a
score back of 1 for all the docs.
If I add a simple Field Value function query to the constant score
query, as in: *:* _val_:price_f, the query norm
13 matches
Mail list logo
