[
https://issues.apache.org/jira/browse/SOLR-14102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004061#comment-17004061
]
Mikhail Khludnev commented on SOLR-14102:
-----------------------------------------
After thinking a little it turns doubtful to me. I seems like custom search
component hits only portion of shards, but faceting might hit all of them eg
for refining. It looks like a design flaw. I suppose _something_ (whether it
custom component or handles) should set shards subset in the early beginning of
request handling and all components should work with the same set of shards.
> FacetModule use number of responses from shards as number of shards
> -------------------------------------------------------------------
>
> Key: SOLR-14102
> URL: https://issues.apache.org/jira/browse/SOLR-14102
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tomohiro Manabe
> Priority: Major
> Attachments: SOLR-14102.patch
>
>
> Hi, I am developing a SearchComponent which sends some requests to only a
> part of shards.
> Basically it works well, but using it with facetting triggers an error.
> I found that FacetModule use the number of responses from shards
> (sreq.responses.size()) as the number of shards.
> Of course this assumption is incorrect in case that only a part of shards
> respond.
> Instead of the number of responses, using rb.shards.length may be better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]