lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27868] - Bad performance in PrefixQuery for large indices.
Date Tue, 13 Apr 2004 17:16:49 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27868>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27868

Bad performance in PrefixQuery for large indices.





------- Additional Comments From paul.elschot@xs4all.nl  2004-04-13 17:16 -------
There is no bug here. 
 
PrefixQuery uses a TermEnum is used from IndexReader.terms(). 
The term enumerator will give only unique terms from the term index. 
There will be no identical TermQuery's generated. 
 
(A Termdocs from IndexReader.termDocs(Term) would do the repetitions 
you are considering.) 
 
The prefix is tested before the field because it normally is 
the first one that fails. In case this test passes, one still 
has to check the field anyway, so it doesn't matter much. 
 
Modifying add() on BooleanQuery would need to add the 
boosts of the clauses in case two equal TermQuery clauses are added, 
otherwise existing scoring behaviour would be broken. 
 
Regards, 
Paul

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


Mime
View raw message