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

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.3
• Component/s: update
• Assignee: Noble Paul
• Reporter: Jayson Minard
• Created: 13/May/09 18:14
• Updated: 02/May/13 02:29

Description

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.

Issue Links

• blocks: SOLR-3038 Solrj should use javabin wireformat by default with updaterequests
• depends upon: SOLR-1162 SolrJ UpdateRequest does not maintain order of operations when sending mixed types of changes (updates, delete id, delete query, update iterator)
• is related to: SOLR-2699 Add SolrInputDocument support to javabin format