Erick can you please point me to some example of creating a filtered wildcard
query. I have not used filters anytime before. Tried reading but still am
really not able to understand how filters actually work and will help me
getting rid of MaxClause Exception.
Regards,
Ruchika
Erick
I'll see if I can get back to this over the weekend.
I got a chance to copy my corpus to another G4 and try indexing with
Lucene 2.2. This one seems OK! Same texts. So now I'm inclined to
believe that it *is* the machine, rather than the code. Whew! Though
that doesn't explain why 2.0 works
My question is for anyone who has experience with Lucene's SpellChecker,
especially around its performance characteristics/ramifications.
1. Given the fact that SpellChecker expands a query by adding all the
permutations of potentially misspelled word, how does it perform in general?
2. How are
Hmmm, it still sounds like you are hitting a threading issue that is
probably exacerbated by the multicore platform of the newer machine.
Is there anyway to put together a unit test that we can try?
Thanks,
Grant
On Dec 2, 2007, at 9:10 PM, Bill Janssen wrote:
I'll see if I can get back
On Dec 2, 2007 9:28 PM, Grant Ingersoll [EMAIL PROTECTED] wrote:
Hmmm, it still sounds like you are hitting a threading issue that is
probably exacerbated by the multicore platform of the newer machine.
Exactly what I was thinking.
What are the details of the CPUs of these two systems?
-Yonik
Suppose I have an index containing the terms impostor, imposter, fraud, and
fruad, then presumably regardless of whether I spell impostor and fraud
correctly, Lucene SpellChecker will offer the improperly spelled versions as
corrections. This means that the phrase The login fraud involves an
Hmmm, it still sounds like you are hitting a threading issue that is
probably exacerbated by the multicore platform of the newer machine.
Exactly what I was thinking.
What are the details of the CPUs of these two systems?
Ah, good point. The bad machine is a dual-processor 1GHz G4 wind
MultiReader is more efficient and is preferred when possible.
MultiSearcher allows further functionality.
Every time an index has more than a single segment (which is.
to say almost every index except for after calling optimize()),
Opening an IndexReader (or an IndexSearcher) above that index),
This is from Lucene's CHANGES.txt:
LUCENE-773: Deprecate the FSDirectory.getDirectory(*) methods that
take a boolean create argument. Instead you should use
IndexWriter's create argument to create a new index.
(Mike McCandless)
So you should create the FSDir with
