: How come if bq doesn't influence what matches -- that's q -- bq only
: influence
: the scores of existing matches if they also match the bq
because that's the way it was designed ... "bq" is "boost query" it's
designed to boost the scores of documents that match the "q" param.
: when I put
t set will be sorted by q
> : (relevance)?
>
> no. bq doesn't influence what matches -- that's q -- bq only influence
> the scores of existing matches if they also match the bq.
>
>
>
> -Hoss
>
>
>
--
View this message in context:
http://www.nabble.com/the-time-factor-tp17204792p22413452.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hello Chris,
> : If this is how it works, it sounds like the bq will be used first
> : to get a result set, then the result set will be sorted by q
> : (relevance)?
> no. bq doesn't influence what matches -- that's q -- bq only influence
> the scores of existing matches if they also match the bq
: I'm not quite understanding how boost query works though. How does it
: "influence" the score exactly? Does it just simply append to the "q"
: param? From the wiki:
Esentially yes, but documents must match the at least one clause of
the "q", matching the "bq" is optional (and when it happens,
Hello Chris,
> it sounds like you only attempted tweaking the boost value, and not
> tweaking the function params ... you can change the curve so that really
> new things get a large score increase, but older things get less of an
> increase.
recip(rord(creationDate),1,a,b)^w
I was tweaking the
: similar. In my case, if I want to rank the most recent documents first
: (because it's about news), I have to use very large boost, which will
: end up getting the docs that are not so relevant to the top. I haven't
it sounds like you only attempted tweaking the boost value, and not
tweaking t
- Solr - Nutch
- Original Message
> From: JLIST <[EMAIL PROTECTED]>
> To: Otis Gospodnetic
> Sent: Tuesday, May 20, 2008 4:32:05 PM
> Subject: Re[2]: the time factor
>
> Hello Otis,
>
> Could you be a bit more specific or point me to some documentation
> page
> - Original Message
>> From: Jack <[EMAIL PROTECTED]>
>> To: solr-user@lucene.apache.org
>> Sent: Tuesday, May 20, 2008 3:59:06 PM
>> Subject: Re: the time factor
>>
>> Hi Otis,
>>
>> I tried this. It doesn't seem to solve my pr
gt; To: solr-user@lucene.apache.org
> Sent: Tuesday, May 20, 2008 3:59:06 PM
> Subject: Re: the time factor
>
> Hi Otis,
>
> I tried this. It doesn't seem to solve my problem, though. I think
> it's best used to make small adjustment when relevance scores are
> sim
Hi Otis,
I tried this. It doesn't seem to solve my problem, though. I think
it's best used to make small adjustment when relevance scores are
similar. In my case, if I want to rank the most recent documents first
(because it's about news), I have to use very large boost, which will
end up getting
Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
> - Original Message
>> From: JLIST <[EMAIL PROTECTED]>
>> To: solr-user@lucene.apache.org
>> Sent: Tuesday, May 13, 2008 5:42:38 AM
>> Subject: the time factor
>>
>> Hi
sfactory, either,
> because one source may update more frequently than the
> others and it tends to occupy the first rows most of
> the time. I wonder what is the best way of combining the
> time factor in news search?
>
> Thanks,
> Jack
the
others and it tends to occupy the first rows most of
the time. I wonder what is the best way of combining the
time factor in news search?
Thanks,
Jack
13 matches
Mail list logo
