[
https://issues.apache.org/jira/browse/LUCENE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Israel Tsadok updated LUCENE-1178:
----------------------------------
Actually, when using the other search methods, e.g. search(query, filter, n),
the proper method is called (createWeight), so this works properly if you don't
use Hits - MultiSearcher's method is the one that gets called.
There was a similarity issue in MultiSearcher, but LUCENE-789 fixed it.
> Hits does not use MultiSearcher's createWeight
> ----------------------------------------------
>
> Key: LUCENE-1178
> URL: https://issues.apache.org/jira/browse/LUCENE-1178
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.3
> Reporter: Israel Tsadok
> Attachments: hits.diff
>
>
> I am developing a distributed index, using MultiSearcher and RemoteSearcher.
> When investigating some performance issues, I noticed that there is a lot of
> back-and-forth traffic between the servers during the weight calculation.
> Although MultiSearcher has a method called createWeight that minimizes the
> calls to the sub-searchers, this method never actually gets called when I
> call search(query).
> From what I can tell, this is fixable by changing in Hits.java the line:
> weight = q.weight(s);
> to:
> weight = s.createWeight(q);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
