I have a simple request that applies to org.apache.lucene.util.Parameter, but
before I go suggesting things to add to Lucene, a quick introduction: I'm Joe,
I'm working for a company that's using Lucene to build large-ish indexes of
documents for clients who'd like to securely store their digital
Oops - I just realized you're maintaining a static map of these parameters in
the Parmeter class. Should have looked more closely before writing - sorry
'bout that.
Glad I at least got the intro correct.
-j
--- Joe R <[EMAIL PROTECTED]> wrote:
>
> I have a simple r
Hello,
I'm trying to write a MultiSearcher/ParallelMultiSearcher variation that uses
JMS to talk to its subordinate Searchers. While running through MultiSearcher
to see where I can save some cycles or network hops, I came across
Query.combine(). It's called from MultiSearcher.rewrite() (as you
nchmarked this, but I've always believed that
> caching the df's on the central server would be a significant benefit.
>
> Chuck
>
>
> Joe R wrote on 05/30/2006 11:32 AM:
> > Hello,
> >
> > I'm trying to write a MultiSearcher/ParallelMultiSearch
We faced what might be a similar problem not too long ago. Our app is supposed
to allow for foldering -- i.e., a document may be in one or more folders that
the user creates and populates by hand or via query. We used a simple btree
database from Berkeley JE and used a hit collector to filter ag
