[ https://issues.apache.org/jira/browse/SOLR-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yonik Seeley reassigned SOLR-659: --------------------------------- Assignee: Yonik Seeley > Explicitly set start and rows per shard for more efficient bulk queries > across distributed Solr > ----------------------------------------------------------------------------------------------- > > Key: SOLR-659 > URL: https://issues.apache.org/jira/browse/SOLR-659 > Project: Solr > Issue Type: Improvement > Components: search > Affects Versions: 1.3 > Reporter: Brian Whitman > Assignee: Yonik Seeley > Priority: Minor > Fix For: 1.4 > > Attachments: shards.start_rows.patch, SOLR-659.patch > > > The default behavior of setting start and rows on distributed solr (SOLR-303) > is to set start at 0 across all shards and set rows to start+rows across each > shard. This ensures all results are returned for any arbitrary start and rows > setting, but during "bulk queries" (where start is incrementally increased > and rows is kept consistent) the client would need finer control of the > per-shard start and rows parameter as retrieving many thousands of documents > becomes intractable as start grows higher. > Attaching a patch that creates a &shards.start and &shards.rows parameter. If > used, the logic that sets rows to start+rows per shard is overridden and each > shard gets the exact start and rows set in shards.start and shards.rows. The > client will receive up to shards.rows * nShards results and should set rows > accordingly. This makes bulk queries across distributed solr possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.