[ 
https://issues.apache.org/jira/browse/SOLR-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670431#comment-13670431
 ] 

Joel Bernstein edited comment on SOLR-4816 at 5/30/13 4:01 PM:
---------------------------------------------------------------

Latest patch is a version of CloudSolrServer that: 

1)Does document routing
2)Sends requests to each shard in a separate thread
3) Uses javabin transport 
4) Is backwards compatible with both the response and exception. 

It does this all by default, no switches needed.

This is accomplished by returning a response or throwing an exception that 
condenses the info from each shard into a single response or exception.

To get the full info for the response or exception you can down cast to either 
RouteReponse or RouteException which gives you a detailed breakdown from each 
of the shards.

Will update the ticket name and description accordingly.


                
      was (Author: joel.bernstein):
    Latest patch is a version of CloudSolrServer that: 

1)Does document routing
2)Sends requests to each shard in a separate thread
3) Uses javabin transport 
4) Is backwards compatible with both the response and exception. 

It does this all by default, no switches needed.

I accomplish this by returning a response or throwing an exception that 
condenses the info from each shard into a single response or exception.

To get the full info for the response or exception you can down cast to either 
RouteReponse or RouteException which gives you a detailed breakdown from each 
of the shards.

Will update the ticket name and description accordingly.


                  
> Add document routing to CloudSolrServer
> ---------------------------------------
>
>                 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.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.patch, 
> SOLR-4816.patch, SOLR-4816.patch, SOLR-4816-sriesenberg.patch
>
>
> This issue adds the following enhancements to CloudSolrServer's update logic:
> 1) Document routing: Updates are routed directly to the correct shard leader 
> eliminating document routing at the server.
> 2) Parallel update execution: Updates for each shard are executed in a 
> separate thread so parallel indexing can occur across the cluster.
> 3) Javabin transport: Update requests are sent via javabin transport.
> These enhancements should allow for near linear scalability on indexing 
> throughput.
> Usage:
> CloudSolrServer cloudClient = new CloudSolrServer(zkAddress);
> SolrInputDocument doc1 = new SolrInputDocument();
> doc1.addField(id, "0");
> doc1.addField("a_t", "hello1");
> SolrInputDocument doc2 = new SolrInputDocument();
> doc2.addField(id, "2");
> doc2.addField("a_t", "hello2");
> UpdateRequest request = new UpdateRequest();
> request.add(doc1);
> request.add(doc2);
> request.setAction(AbstractUpdateRequest.ACTION.OPTIMIZE, false, false);
> NamedList response = cloudClient.request(request); // Returns a backwards 
> compatible condensed response.
> //To get more detailed response down cast to RouteResponse:
> CloudSolrServer.RouteResponse rr = (CloudSolrServer.RouteResponse)response;
> NamedList responses = rr.getRouteResponse(); 

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to