> Really? because I see your description of the situation as mixing two totally > different things:
They are connected because they follow each other. > 1. a situation where a distributed case returns scores different than a single > node case. Who cares? This should be up to the user to make the > appropriate tradeoffs (e.g. deciding to use distributed IDF or not, or even > different types of caching impls like andrzej hinted at, or whatever)... but > its > not "wrong". I just mentioned that for queries that rewrite to different queries on each node (like MTQ because TermsEnums are different) will even not produce comparable scores with a global IDF - that’s what I wanted to say. The connection is here: The buggy MultiSearcher tried to prevent this by combining the rewritten queries and that caused the deMorgan bug. > 2. a situation where your query is A NOT B and it then returns B. This was the > real problem with MultiSearcher, and this is just wrong. About the merging; when I look at Mikes code: Except the global IDF and the bug in MTQ, the merging code is identical to what MultiSearcher did before. I would in trunk even recommend to undelete FieldDocSortedHitQueue and you have everything you need to merge two TopDocs instances. Uwe --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
