[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708789#action_12708789
]
Jayson Minard commented on SOLR-1162:
-------------------------------------
In response to Noble Paul:
An UpdateRequest currently contains: a list of adds, a single add via
iterator, a list of delete by ids, a list of delete queries. So you can pile
them all into the same object currently and then have no idea what order they
will actually execute. If you want to stream adds, you cannot intermix deletes
or other actions in the same stream. So if UpdateRequest is going to allow a
set of different actions it should at least maintain the order in which they
were added and execute them similarly.
UpdateRequest is the current batching model, so it should be correct.
> SolrJ does not maintain order of operations when using an UpdateRequest
> object to send them in bulk
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-1162
> URL: https://issues.apache.org/jira/browse/SOLR-1162
> Project: Solr
> Issue Type: Bug
> Components: clients - java
> Affects Versions: 1.3
> Reporter: Jayson Minard
> Attachments: Solr-1162.patch
>
>
> In SolrJ UpdateRequest object it maintains separate lists of documents to
> add, delete, and delete queries so that the order of those operations is not
> known to the caller. It really should execute the items in the same order
> they were added to the UpdateRequest.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
