[jira] [Commented] (SOLR-7580) Number of ScoreDoc instances equals rows parameter, not actual number of matches

["c sudhakar reddy (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17573661#comment-17573661 ] 

c sudhakar reddy commented on SOLR-7580:
----------------------------------------

Any update on this to get the all the rows as per search criteria instead of 10 rows 

> Number of ScoreDoc instances equals rows parameter, not actual number of matches
> --------------------------------------------------------------------------------
>
>                 Key: SOLR-7580
>                 URL: https://issues.apache.org/jira/browse/SOLR-7580
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 5.1
>            Reporter: Markus Jelsma
>            Priority: Major
>             Fix For: 5.5, 6.0
>
>
> We have several batch jobs that use StreamingResponseCallback to collect all records matching a specific query. For each record, we execute a new query and need all results without paging through them. Because we do not know the amount of matches to expect, we do setRows(Integer.MAX_VALUE);. According to the VisualVM samples, this results in a huge amount of ScoreDoc instances, making the query unreasonably slow.
> The current work-around we use is to execute the same query with setRows(0), get numResults, and then reissue the query with setRows(numResults). This is fast, almost as fast as one would expect.
> This is, however, a very dirty work-around. I am unsure whether this is a Solr or Lucene issue, SolrIndexSearcher is a beast to debug ;)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org