changing prefix queries to use a filter instead of expanding terms

[Jack McBane <ja...@gmail.com>]

Hi all,

I've been using lucene for some number of months now and for the most part
it has worked great. One thing that we have had problems with is prefix
queries expanding to the point of making the search fail due to many terms.
The part of our application that this happens is people entering the first
part of a part number which is practically a unique key and we don't really
care about having contribute to the score of the hit. Along those lines I
was thinking about adding some functionality to the code that expands prefix
queries to create a filter and use that instead of just expanding the
individual terms. Can anyone see any major issues with doing it this way?
Has anyone else tried to do something like this? Any pointers on what I
should be looking at or maybe gotchas to avoid?

Any advice would be appreciated.

Thanks.

Re: changing prefix queries to use a filter instead of expanding terms

[Chris Hostetter <ho...@fucit.org>]

: care about having contribute to the score of the hit. Along those lines I
: was thinking about adding some functionality to the code that expands prefix
: queries to create a filter and use that instead of just expanding the
: individual terms. Can anyone see any major issues with doing it this way?

Not at all, in fact the same idea has already been commited for
RangeQueries, and maybe if we poke Yonik real nicely, he'll cleanup/commit
the version of PrefixFilter he already wrote and mentioned in
passing here...

https://issues.apache.org/jira/browse/LUCENE-383



-Hoss


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