[jira] Commented: (SOLR-1164) BinaryUpdateRequestHandler and JavaBinUpdateRequestCodec do not maintain order of the commands as serialized in the binary format

["Jayson Minard (JIRA)" <ji...@apache.org>]

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

Jayson Minard commented on SOLR-1164:
-------------------------------------

Noticed that SolrJ classes are used in the server to implement the handler side which makes it hard to split the patch.  If we want to clean that up, the patch can be split but otherwise leaving it in SOLR-1162 and tracking both sides of the coin by leaving this issue here.

> 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
>
> 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.