[
https://issues.apache.org/jira/browse/SOLR-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747567#action_12747567
]
Martijn van Groningen commented on SOLR-1143:
---------------------------------------------
Hi Grant, thanks for mentioning that, I did not realized that.
I have two other ideas about returning a partial result that might be usable in
this patch:
1) Currently when a partial result is returned the response does not tell you
which shard has failed, it only tells you that it is a partial result. Wouldn't
it be handy to include hostnames or ip addresses in the response of the shards
that had a connection timeout?
2) A partial result is only returned when when a connection exception occurs,
is it practical to return a partial result when another type of exception
occurs? Let say one shard has a corrupted index and therefore while searching
only that shard throws an exception, I can imagine that in such situation it is
also useful to return a partial result instead of only returning an error for
the complete search. a
> Return partial results when a connection to a shard is refused
> --------------------------------------------------------------
>
> Key: SOLR-1143
> URL: https://issues.apache.org/jira/browse/SOLR-1143
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Nicolas Dessaigne
> Assignee: Grant Ingersoll
> Fix For: 1.4
>
> Attachments: SOLR-1143-2.patch, SOLR-1143-3.patch, SOLR-1143.patch
>
>
> If any shard is down in a distributed search, a ConnectException it thrown.
> Here's a little patch that change this behaviour: if we can't connect to a
> shard (ConnectException), we get partial results from the active shards. As
> for TimeOut parameter (https://issues.apache.org/jira/browse/SOLR-502), we
> set the parameter "partialResults" at true.
> This patch also adresses a problem expressed in the mailing list about a year
> ago
> (http://www.nabble.com/partialResults,-distributed-search---SOLR-502-td19002610.html)
> We have a use case that needs this behaviour and we would like to know your
> thougths about such a behaviour? Should it be the default behaviour for
> distributed search?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
