[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-user
Subject:    RE: Help with indexing and query strategy
From:       "Colin Young" <Colin.Young () tembizi ! com>
Date:       2006-01-31 3:51:14
Message-ID: 3AF76382C31760418AF0FBFD84F714030A7176A3 () MI8NYCMAIL07 ! Mi8 ! com
[Download RAW message or body]

I have thought about that. I couldn't figure out a way to make it work.
Fortunately, I have managed to solve the problem (excepting prefix or
wildcard searches) which is very close to what Rajesh suggested (also
see my response to his response).

Thanks for taking a look.

Colin 

-----Original Message-----
From: Jeff Rodenburg [mailto:jeff.rodenburg@gmail.com] 
Sent: 30 January, 2006 18:38
To: java-user@lucene.apache.org
Subject: Re: Help with indexing and query strategy

Have you considered evaluating doc-score thresholds for limiting your
results?  Since the perfect answers to these situations lie in the
constant tweaking and twiddling of analysis and tokenization, one way
I've found to help is to evaluate result scores.  In your "Ontario CA"
example, limiting results to two vs. three vs. four is not necessarily
so important as getting the first results accurate.

Without seeing your test code, I'm guessing that a search for "Ontario
CA"
returns [3] and [4] ahead of any other results.  You could try looking
at the score for each returned hit, and based on some threshold (80-20
rule,
maybe) display what's returned.

Just a thought.

-- j

Notice: This email message is for the sole use of the intended recipient(s) and may \
contain confidential and privileged information. Any unauthorized review, use, \
disclosure or distribution is prohibited. If you are not the intended recipient, \
please contact the sender by reply email and destroy all copies of the original \
message.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic