I didn't see any response so I wanted to check if my observation simply is not
relevant for other people or if I missed to provide any required details.
Thanks!
-Original Message-
Date: 05/09/2019 08:28 AM
Subject: Negative boost query (bq) with edismax for lower scores with Solr
I find that the edismax boost query implementation is not quite logical. It
does not allow selectively decreasing the relevancy score anymore.
E.g. bq=color:red^2 can be added to increase the score of matching documents.
But how can I decrease the score for documents with color:red? Before Solr
Hi,
I’m trying to boost all results using the bq param with edismax where termA and
termB do not appear in the field, but if phraseC appears it doesn’t matter if
termA and termB appear.
The following works and boosts everything that doesn’t have termA and termB in
myField so the effect is that
I understand that the only way to simulate a negative boost is to positively
boost the inverse. I have looked at
http://wiki.apache.org/solr/SolrRelevancyFAQ but I think I am missing
something on the formatting of my query. I am using:
http://localhost:8983/solr/search?q=dog&am
Hi all,
I understand that the only way to simulate a negative boost is to positively
boost the inverse. I have looked at
http://wiki.apache.org/solr/SolrRelevancyFAQ but I think I am missing
something on the formatting of my query. I am using:
http://localhost:8983/solr/search?q=dog&am
I think the key was change the tie to 0. I had it at 0.1. Getting
exactly what I want now.
Big thanks for the help.
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Monday, March 29, 2010 5:20 PM
To: solr-user@lucene.apache.org
Subject: RE: negative boost
I
dismax.
Thanks for the tip. I will try it.
Jason
-Original Message-
From: Chris Hostetter [mailto:hossman_luc...@fucit.org]
Sent: Monday, March 29, 2010 5:06 PM
To: solr-user@lucene.apache.org
Subject: RE: negative boost
: Unfortunately, my results aren't quite what I want unless I
: Unfortunately, my results aren't quite what I want unless I use 0 on the
: second field. Instead, if something matches in all the fields it is
: elevated to the top. I only want the first field match elevated to the
: top and I want all first field matches to have the same weight. Next, I
-
From: Paul Libbrecht [mailto:p...@activemath.org]
Sent: Monday, March 29, 2010 1:10 PM
To: solr-user@lucene.apache.org
Subject: Re: negative boost
Jason,
don't you want
field1^3 * field2^1 * field3^0.9
?
As written in Lucene in action, it's all multiplied.
So "negative bo
Jason,
don't you want
field1^3 • field2^1 • field3^0.9
?
As written in Lucene in action, it's all multiplied.
So "negative boost" means "boost under 1"
(and probably elsewhere)
paul
PS: take the log and you get this negative.
Le 29-mars-10 à 21:08, Jason Chaf
Is it possible to give a negative in boost in dismax? For instance,
field1^3 field2^0 field3^-0.1
Thanks,
Jason
ld_a:54"
>
> adding a boost value "^1" to a negated clause doesn't do much (except
> maybe make hte queryNorm really wacky)
>
>
> -Hoss
>
>
>
--
View this message in context:
http://old.nabble.com/weird-behaviour-when-setting-negative-boost-with-bq-using-dismax-tp27406614p27461856.html
Sent from the Solr - User mailing list archive at Nabble.com.
: bq=(*:* -field_a:54^1)
I think what you want there is bq=(*:* -field_a:54)^1
...you are "boosting" things that don't match "field_a:54"
adding a boost value "^1" to a negated clause doesn't do much (except
maybe make hte queryNorm really wacky)
-Hoss
>Generally speaking, by convention boosts in Lucene have unity at 1.0,
>not 0.0. So, a "negative boost" is usually done with boosts between 0
>and 1. For this case, maybe a boost of 0.1 is what you want?
I forgot to say I tried what you say aswell but didn't work.
In the standard query parser, this means "remove all entries in which
field_a = 54".
> bq=-field_a:54^1
Generally speaking, by convention boosts in Lucene have unity at 1.0,
not 0.0. So, a "negative boost" is usually done with boosts between 0
and 1. For this case, m
work. What seems to happen is that results that match
field_a:54 are excluded. Just like doing:
fq=-field_a:54
Any idea what could be happening? Has anyone experienced this behaviour
before?
Thnaks in advance
--
View this message in context:
http://old.nabble.com/weird-behabiour-when-setting-neg
),
and it doesn't return any results if only the first clause is present (the
one with negative boost) even though it's a matching clause.
I think this is related to the fact that in TopScoreDocCollector:48 the
pqTop.score is initialized to 0, and then all results that have lower score
tha
ilter, int),
> and it doesn't return any results if only the first clause is present (the
> one with negative boost) even though it's a matching clause.
>
> I think this is related to the fact that in TopScoreDocCollector:48 the
> pqTop.score is initialized to 0, and then all
now Lucene 2.9 no longer
does either.
Hmm ... The code that I pasted in my previous email uses
Searcher.search(Query, int), which in turn uses search(Query, Filter,
int), and it doesn't return any results if only the first clause is
present (the one with negative boost) even though i
On Mon, Oct 12, 2009 at 5:58 AM, Andrzej Bialecki wrote:
> BTW, standard Collectors collect only results
> with positive scores, so if you want to collect results with negative scores
> as well then you need to use a custom Collector.
Solr never discarded non-positive hits, and now Lucene 2.9 no
Yonik Seeley wrote:
On Sun, Oct 11, 2009 at 6:04 PM, Lance Norskog wrote:
And the other important
thing to know about boost values is that the dynamic range is about
6-8 bits
That's an index-time boost - an 8 bit float with 5 bits of mantissa
and 3 bits of exponent.
Query time boosts are norm
On Sun, Oct 11, 2009 at 6:04 PM, Lance Norskog wrote:
> And the other important
> thing to know about boost values is that the dynamic range is about
> 6-8 bits
That's an index-time boost - an 8 bit float with 5 bits of mantissa
and 3 bits of exponent.
Query time boosts are normal 32 bit floats.
e).
> We could solve our problem this way.
>
>
> We wanted to do negatively boost some documents based on certain keywords
> while
>
> Marc Sturlese wrote:
>>
>>
>> :>the only way to "negative boost" is to "positively boost" the inverse...
documents based on certain keywords
while
Marc Sturlese wrote:
>
>
> :>the only way to "negative boost" is to "positively boost" the inverse...
> :>
> :>(*:* -field1:value_to_penalize)^10
>
> This will do the job aswell as bq supports
:>the only way to "negative boost" is to "positively boost" the inverse...
:>
:> (*:* -field1:value_to_penalize)^10
This will do the job aswell as bq supports pure negative queries (at least
in trunk):
bq=-field1:value_to_penalize^10
http://wiki.apache.o
: Use decimal figure less than 1, e.g. 0.5, to express less importance.
but that's stil la positive boost ... it still increases the scores of
documents that match.
the only way to "negative boost" is to "positively boost" the inverse...
(*:* -field1:value_
Hi,
Use decimal figure less than 1, e.g. 0.5, to express less importance.
Koji
Larry He wrote:
Hi all,
I am looking for a way to assign negative boost to a term in Solr query.
Our use scenario is that we want to boost matching documents that are
updated recently and penalize those that have
Hi all,
I am looking for a way to assign negative boost to a term in Solr query.
Our use scenario is that we want to boost matching documents that are
updated recently and penalize those that have not been updated for a long
time. There are other terms in the query that would affect the scores
28 matches
Mail list logo
