[
https://issues.apache.org/jira/browse/SOLR-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711460#action_12711460
]
Noble Paul commented on SOLR-1164:
----------------------------------
yes. apply SOLR-1162 over this patch.if any changes are required for this issue
we can do it
Another suggestion for 1162
you may not need so many new classes for each type of request.
Just keep one NamedList in the UpdateRequest object and keep adding items to
that with proper names. say docs,deleteByid,DeleteByQ etc. that can make it
very simple
> BinaryUpdateRequestHandler and JavaBinUpdateRequestCodec do not maintain
> order of the commands as serialized in the binary format
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-1164
> URL: https://issues.apache.org/jira/browse/SOLR-1164
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 1.3
> Reporter: Jayson Minard
> Assignee: Noble Paul
> Attachments: SOLR-1164.patch, SOLR-1164.patch
>
>
> When sending commands in the Java binary format to the
> BinaryUpdateRequestHandler it does not process them in the order received.
> It processes all add/updates then delete by id then delete by query
> regardless of what is sent. See SOLR-1162 for related issue and patch that
> covers both issues (they are intertwined since some classes are shared on
> both sides of the wire)
> I wanted a separate issue covering this so that it is seen from the server
> viewpoint and not just as a client API issue as other clients writing the
> binary form would be unable to maintain order of commands as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
