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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
