If the Chained filter works off of the cached QueryFilters, then that is
great and I don't mind not caching the ChainedFilter and doing the work
to combine those bit vectors (assuming that is what it is doing). I
want to build up a set of small QueryFilters and that can be cached and
be combined in any order (using the ChainedFilter operations) while
still making use of caching. If ChainedFilter does this (or doesn't),
it would be nice to have it mentioned in the API docs.
Les
Chris Hostetter wrote:
: I have a question about filter caching. I have a lot of QueryFilters
: that I use when searching that filter on a single field. Sometimes
: alone I use them by themselves, but mostly I use them in some
: combination using ChainedFilter. Does the caching take advantage of
: only the final filter that used in the query, or would a ChainedFilter
: (say 'A and B and C') make use of the cached versions of the single
: field QueryFilters A,B and C and just combine their bitsets?
the individual QueryFilter's cache themselves, if you want a ChainedFilter
composed of those QueryFilter's to be cached you should wrap it in a
CachingWrapperFilter.
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
