Re: flexibility.
This boost does decays over time, the further it gets from now the less
of a boost it receives. You are right though, it doesn't allow a fine
degree of control, particularly if you don't want to smoothly decay the
boost. I hadn't considered your suggestion, so I'll keep it in mind if
the need arises.
Re: Adding boost to query:
I am no expert, but I did this and it worked:
SolrJ: solrQuery.setQuery("{!boost
b=recip(ms(NOW,publishdate),3.16e-11,1,1)} " + queryparam);
Where queryparam is what you are searching for. You quite literally
just prepend it.
Via http://localhost:8080/apache-solr-1.4.0/select, just prepend it to
your q= like this:
q={!boost+b%3Drecip(ms(NOW,publishdate),3.16e-11,1,1)}+findthis
Tim
-----Original Message-----
From: Shawn Heisey [mailto:[email protected]]
Sent: Wednesday, July 14, 2010 1:16 PM
To: [email protected]
Subject: Re: date boosting and dismax
One of the replies I got on a previous thread mentioned range queries,
with this example:
[NOW-6MONTHS TO NOW]^5.0 ,
[NOW-1YEARS TO NOW-6MONTHS]^3.0
[NOW-2YEARS TO NOW-1YEARS]^2.0
[* TO NOW-2YEARS]^1.0
Something like this seems more flexible, and into it, I read an
implication that the performance would be better than the boost function
you've shown, but I don't know how to actually put it into a URL or
handler config.
I also seem to remember seeing something about how to do "less than" in
range queries as well as the "less than or equal to" implied by the
above, but I cannot find it now.
Thanks,
Shawn
On 7/14/2010 10:26 AM, Tim Gilbert wrote:
> I used this before my search term and it works well:
>
> {!boost b=recip(ms(NOW,publishdate),3.16e-11,1,1)}
>
> Its enough that when I search for *:* the articles appear in
> chronological order.
>
> Tim
