[
https://issues.apache.org/jira/browse/SOLR-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748986#action_12748986
]
Yonik Seeley commented on SOLR-659:
-----------------------------------
I agree this makes sense to enable efficient bulk operations, and also fits in
with a past idea I had about mapping shards.param=foo to param=foo during a
sub-request.
I'll give it a couple of days and commit if there are no objections.
> 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
> 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.
