You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2013/03/23 01:35:15 UTC
[jira] [Closed] (SOLR-1524) proposal on distributed search
[ https://issues.apache.org/jira/browse/SOLR-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl closed SOLR-1524.
-----------------------------
Resolution: Duplicate
Continue discussions in SOLR-1726 which tries to solve the same issue
SPRING_CLEANING_2013
> proposal on distributed search
> ------------------------------
>
> Key: SOLR-1524
> URL: https://issues.apache.org/jira/browse/SOLR-1524
> Project: Solr
> Issue Type: Sub-task
> Components: clients - java
> Reporter: johnson.hong
>
> Hi,all.
> some days ago,I put a question that "why it gets slower while keep on increasing the start value accross distributed search ?".
> And one reply by Shalin Shekhar Mangar was "distributed search fetches start+rows documents from each shard in order to correctly merge the results".
> After this I read the source code,and I found query across distributed search would be separated into nshards' query.
> Each shard query will be excute as follows:
> 1.get ids of matched documents into DocList //take little time
> 2.get all documents by id which result in step 1. //take little time
> 3.write all the documents found to binary string
> 4.parse the binary string back to SolrDocumentList // step 4 take almost all the time used
> From above,I propose :It is not necessary to execute step 3 and step 4 even step 2,the ids found is enough to merge results,isn't it?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org