[
https://issues.apache.org/jira/browse/SOLR-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583733#comment-13583733
]
vinay pothnis commented on SOLR-4486:
-------------------------------------
The solr-users mailing list thread for reference:
http://lucene.472066.n3.nabble.com/solr-cloud-4-1-Issue-with-order-in-a-batch-of-commands-td4041367.html
> The order of commands is not maintained in a batch of adds/updates and deletes
> ------------------------------------------------------------------------------
>
> Key: SOLR-4486
> URL: https://issues.apache.org/jira/browse/SOLR-4486
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 4.1
> Reporter: vinay pothnis
>
> I have the following set up:
> * solr cloud 4.1.0
> * 2 shards with embedded zookeeper
> * plain http to communicate with solr
> I am testing a scenario where i am batching multiple commands and sending
> to solr. Since this is the solr cloud setup, I am always sending the
> updates to one of the nodes in the cloud.
> e.g.: http://localhost:8983/solr/sample/update
> *example set of commands:*
> {"add": {"doc":
> {"field-1":"1359591340025","field-2":1361301249330,"doc_id":"e.1.78"}
> },"add": {"doc":
> {"field-1":"1360089709282","field-2":1361301249377,"doc_id":"e.1.78"}
> },"delete": { "id": "e.1.78" }}
> When I include deletes and updates in the batch, sometimes, the order of
> the commands is not maintained.
> Specifically, if the document does not belong to the shard that I am
> communicating with (lets say shard-1), then shard-1 sends the commands to
> "shard-2". In this case, the "deletes" are sent first and then the updates.
> This changes the order that I originally sent.
> Thanks!
> Vinay
--
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]
