Might be the same issue, haven't been able to determine during a step-through on the code exec. You're right, no need to add a new FilteredQuery to the statement, just a search on combinedQuery with a new myCustomFilter. Unfortunately, no joy; same response.
-- j On 9/13/05, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > > : Hits h1 = oMultiSearcher.Search(new FilteredQuery(combinedQuery, new > : myCustomFilter(1))); > : Hits h2 = oMultiSearcher.Search(new FilteredQuery(combinedQuery, new > : myCustomFilter(2))); > > ...do you get the same results if you use... > > Hits h1 = oMultiSearcher.search(combinedQuery, myCustomFilter(1)); > Hits h2 = oMultiSearcher.search(combinedQuery, myCustomFilter(2)); > > ...I'm not sure why you wouldn't use that method call instead anyway. > > This may be another sympton of a bug that worked in the trunk when i > reported it... > > http://issues.apache.org/jira/secure/ViewIssue.jspa?key=LUCENE-366 > > > > -Hoss > >
