1) document boost is periodicaly recomputed with age as a factor (or
log(age)). It should be slow.
2) Use your own Similarity implementation. Use the DefaultSimilarity
with a dynamic document boost. The Map document id -> age or document id
-> date should be cached with Map, ehCache, whirlcache, oscache or bdb
base. Use expiration caching, and be careful, warm up (ie populating the
cache) should be slow.
M.
James Brady a écrit :
Sorry, I really should have directly explained what I was looking to
do: theserverside.com give higher scores to documents that were added
more recently.
I'd like to do the same, without the date boost being too overbearing
(or unnoticeable...) - some ideas on how to approach this would be great.
James
Begin forwarded message:
From: James Brady <[EMAIL PROTECTED]>
Date: 8 March 2008 19:41:56 PST
To: solr-user@lucene.apache.org
Subject: Favouring recent matches
Hello all,
In Lucene in Action, (replicated here:
http://www.theserverside.com/tt/articles/article.tss?l=ILoveLucene),
theserverside.com team say "The date boost has been really important
for us".
I'm looking for some advice on the best way to actually implement
this - the only way I can see to do it right now is to set a boost
for documents at index time that increases linearly over time.
However, I'm wary of skewing Lucene's scoring in some strange way, or
interfering with the document boosts I'm setting for other reasons.
Any suggests?
Thanks
James
