Hi Erick, thank you for your prompt answer. What do you mean by loading the document? Accessing one of the stored fields? In that case I'm afraid I would need to do it. For example, in the aforementioned case of a result of products, I have to look at any product store_id, which is stored along the document. Is this a performance killer? Maybe I should keep some tables in memory, for example an array mapping from id to store_id in O(1). I will do some benchmarking before anyway.
Cheers, Carlos On 5/24/07, Erick Erickson <[EMAIL PROTECTED]> wrote:
I know of no way to alter the Hits behavior, I recommend using a TopDocs/TopDocCollector. But be aware that if you load the document for each one, you may incur a significant penalty, although the lazy-loading helped me a lot, see FieldSelector..... On 5/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote: > > Hi folks, > > I need to collect some global information from my first 1000 search > results > in order to build up some search refining components containing only > relevant values (those which correspond to at least one of the first 1000 > hits). For example, the results are products and there is a store filter > component that shows only the stores that sells a product between the > first > 1000 hits. So even if the user sees just the first 20, I would have to > inspect the first 1000. I've read that Hits mantains a cache of about 100 > or > 200 hits. Is this configurable? If I could set this cache to 1000 I would > then use Hits to browse the search results. Another way, I should use > HitCollector. What's your advice? > > TIA > Cheers, > Carlos >
