[
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661406#comment-13661406
]
Joel Bernstein commented on SOLR-4816:
--------------------------------------
Stephen's comments brought up other questions which need to be decided in:
1) How to handle delete by requests.
2) How to handle various action requests (commit, optimize etc...).
Probably a good approach to this is to process all the direct updates first and
then remove the document list from the original request and let the original
request execute through the main flow.
I'll work on getting this scenario into the patch.
> 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-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
