hello, hope someone can help explain things to me.
i've been searching for sometime and i have not been able to find
anything to answer my questions.
i'm trying to understand the difference/effects between QueryFilter vs
CachingWrapperFilter and when you would use one vs the other and how
they
On Dec 7, 2004, at 3:06 PM, Ben Rooney wrote:
i'm trying to understand the difference/effects between QueryFilter vs
CachingWrapperFilter and when you would use one vs the other and how
they work exactly.
QueryFilter caches the results (bit set of documents) of a query by
IndexReader.
: executes the search, i would keep a static reference to SearchIndexer
: and then when i want to invalidate the cache, set it to null or create
: design of your system. But, yes, you do need to keep a reference to it
: for the cache to work properly. If you use a new IndexSearcher
: instance
erik, thanks for the reply
i get the filter know and understand how the caching works. however the
caching is only on the filtering level which means i can cache results
that are filtered. but if i do a basic search against the index and
want to cache that, do i need to create my own caching
thanks chris,
you are correct that i'm not sure if i need the caching ability. it is
more to understand right now so that if we do need to implement it, i am
able to.
the reason for the caching is that we will have listing pages for
certain content types. for example a listing page of
If you run the same query again, the IndexSearcher will go all the way
to the index again - no caching. Some caching will be done by your
file system, possibly, but that's it. Lucene is fast, so don't
optimize early.
Otis
--- Ben Rooney [EMAIL PROTECTED] wrote:
thanks chris,
you are
