[
https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709037#action_12709037
]
Jayson Minard commented on SOLR-1162:
-------------------------------------
Outside of UpdateRequest if you hand construct a binary codec stream to send to
Solr (without this patch) your order of actions would not be maintained within
the stream. So the binary streaming update handler is "broken" in this regard
as well.
So this patch actually resolves two issue: UpdateRequest does not serialize
into xml or binary stream the actions in-order. Nor does
BinaryUpdateRequestHandler nor did the underlaying JavaBinUpdateRequestCodec so
these all become unusable for mixed style actions since none can maintain
order. UpdateRequest is just one of the clients to that server-side code that
also has the same issue.
> 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: Improvement
> Components: clients - java
> Affects Versions: 1.3
> Reporter: Jayson Minard
> Attachments: Solr-1162.patch, 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.
