[
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-4816:
---------------------------------
Attachment: SOLR-4816.patch
After spending more time looking at everything that an upateRequest can do I
realized that not all parts of a request are routable.
The latest patch handles this by first sending all the routable updates to the
correct shard. Then executing a final update request with non-routable update
commands such OPTIMIZE or deleteByQuery.
This latest patch has not been tested so is for review purposes only.
> Change CloudSolrServer to send updates to the correct shard
> -----------------------------------------------------------
>
> Key: SOLR-4816
> URL: https://issues.apache.org/jira/browse/SOLR-4816
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.3
> Reporter: Joel Bernstein
> Priority: Minor
> Attachments: SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch,
> SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch, SOLR-4816.patch,
> SOLR-4816.patch, SOLR-4816.patch, SOLR-4816-sriesenberg.patch
>
>
> This issue changes CloudSolrServer so it routes update requests to the
> correct shard. This would be a nice feature to have to eliminate the document
> routing overhead on the Solr servers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
