[
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13657597#comment-13657597
]
Hoss Man commented on SOLR-4816:
--------------------------------
Side note: for testing purposes it's going to be handy to have a
property/setter on CloudSolrServer that forces it to ignore the id and randomly
pick a node to send the updates to, and then have the test framework randomly
set that property -- that way we can future proof ourselves against
accidentally server side bugs where docs aren't sent to the correct shard, or
docs aren't sent to a leader, etc...
> 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
>
>
> This issue adds a "directUpdate" method to CloudSolrServer which 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
