ultisearcher on top. The indexsearcher that uses the small RAMDir can be
> rebinded
> quite often.
>
> /
> Regards
> M
>
>
> -Ursprungligt meddelande-
> Från: Andrzej Bialecki [mailto:[EMAIL PROTECTED]
> Skickat: den 17 januari 2008 10:55
> Till: java-us
r in the background
> after this searcher has been created we are fireing some warm up queries
> against it and after that we change the old searcher to point to the new one.
> Works fine for us and we got large indexes (several millions of articles)...
>
> /Regards
> Marcus
>
/ -- Lucene - Solr - Nutch
- Original Message
From: Tobias Lohr <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Tuesday, January 15, 2008 11:33:56 AM
Subject: Integrating dynamic data into Lucene search/ranking
I have a more architectural question, which is maybe sort of o
I have a more architectural question, which is maybe sort of off topic, but as
I want to implement it using Java and Lucene, it's the right forum however:
I'm thinking of an approach to design a system that integrates dynamic
information into a search (and a ranking) functionality using Lucene.
I'm sorting the search result using multiple fields. Some of them are
"real" fields, within the index, but one is a "pseudo" field, a custom
sort field, implemented by using a custom SortComparatorSource. I end up
with the sorting conditions in exact this order:
1. Sort by score generate by cu
