[
https://issues.apache.org/jira/browse/SOLR-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860143#comment-17860143
]
David Smiley commented on SOLR-13350:
-------------------------------------
I saw an obscure failure for [this
assertion|https://github.com/apache/solr/blob/2fe98d962bb498c29a032708739c9a41e1a263d9/solr/core/src/test/org/apache/solr/search/TestCollapseQParserPlugin.java#L119]
in TestCollapseQParserPlugin.testMultiSort and I have a suspicion that
subtleties in segment processing order from concurrent segment search may have
tickled it. The assertion tests something rather arbitrary, arguably should
not be tested like this -- i.e. it should test that one of the returned docs
has ID 2 or 3 as both are valid answers.
> Explore collector managers for multi-threaded search
> ----------------------------------------------------
>
> Key: SOLR-13350
> URL: https://issues.apache.org/jira/browse/SOLR-13350
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: 9.7
>
> Attachments: SOLR-13350-pre-PR-2508.patch, SOLR-13350.patch,
> SOLR-13350.patch, SOLR-13350.patch
>
> Time Spent: 12h 10m
> Remaining Estimate: 0h
>
> AFAICT, SolrIndexSearcher can be used only to search all the segments of an
> index in series. However, using CollectorManagers, segments can be searched
> concurrently and result in reduced latency. Opening this issue to explore the
> effectiveness of using CollectorManagers in SolrIndexSearcher from latency
> and throughput perspective.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
