seperating requests over 2 ports is a nice solution when having multiple
user-types. I like that althuigh I don't think i need it for this case.
I'm just going to go the 'normal' caching-route and see where that takes me,
instead of thinking it can't be done upfront :-)
Thanks!
hossman wrot
: Although I haven't tried yet, I can't imagine that this request returns in
: sub-zero seconds, which is what I want (having a index of about 1M docs with
: 6000 fields/ doc and about 10 complex facetqueries / request).
i wouldn't neccessarily assume that :)
If you have a request handler whi
ery strings to fetch the filter query. "field:[* TO *]"
> will
> do nicely.
>
> Cheers,
>
> Lance Norskog
>
> -Original Message-
> From: Britske [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 04, 2007 1:38 PM
> To: solr-user@lucene.a
quot; will
do nicely.
Cheers,
Lance Norskog
-Original Message-
From: Britske [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 04, 2007 1:38 PM
To: solr-user@lucene.apache.org
Subject: Re: how to make sure a particular query is ALWAYS cached
hossman wrote:
>
>
> : I want
hossman wrote:
>
>
> : I want a couple of costly queries to be cached at all times in the
> : queryResultCache. (unless I have a new searcher of course)
>
> first off: you can ensure that certain queries are in the cache, even if
> there is a newSearcher, just configure a newSearcher Event L
: I want a couple of costly queries to be cached at all times in the
: queryResultCache. (unless I have a new searcher of course)
first off: you can ensure that certain queries are in the cache, even if
there is a newSearcher, just configure a newSearcher Event Listener that
forcibly warms the
