You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Israel Tsadok (JIRA)" <ji...@apache.org> on 2008/05/28 13:19:45 UTC

[jira] Updated: (LUCENE-1178) Hits does not use MultiSearcher's createWeight

     [ https://issues.apache.org/jira/browse/LUCENE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Israel Tsadok updated LUCENE-1178:
----------------------------------


Wow, that was a deafening silence....

Since Hits has been deprecated in LUCENE-1290, I guess there's no reason to keep this bug open. 
If anyone with permissions is reading this, I think a status change to WONTFIX is in order.

> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org