: 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.
what you are asking for
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 combin
: Essentially what I am trying to do is boost every document by a certain
: factor, so that
: the boost is between 1.0 and 2.0. After this, I we are trying to do a search
: across multiple fields
: and have a computation based purely on tf. Example -
it sounds like you are trying to place too muc
Hi Mike,
I decided to go ahead and upgrade to Lucene 2.1. My regression tests seem
fine. However, I still don't understand the files of the index you've
described.
>>You can also remove all now-deleted filenames if you are only interested
in the most recent snapshot.
I'm not sure what these
On Tuesday 01 May 2007 00:22, [EMAIL PROTECTED] wrote:
> I thought about using ulimit, but it does not scale. In the scenario that
the app has to support, client applications could create hundreds of
thousands of unique properties, which would result in this many indexable
fields.
>
> Based on
