Re: weird behabiour when setting negative boost with bq using dismax

2010-02-04 Thread Marc Sturlese
>: 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" Thanks Hoss. I've updated the Wiki, the content of the bq param was wrong: http://wiki.apache.org/solr/SolrRelevancyFAQ#How_do_I_give_a_very_low

Re: weird behabiour when setting negative boost with bq using dismax

2010-02-04 Thread Chris Hostetter
: 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

Re: weird behabiour when setting negative boost with bq using dismax

2010-02-04 Thread Marc Sturlese
>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 parse

Re: weird behabiour when setting negative boost with bq using dismax

2010-02-03 Thread Lance Norskog
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, maybe a boost of 0.1 is