You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2009/09/17 23:41:57 UTC
[jira] Updated: (SOLR-1164) BinaryUpdateRequestHandler and
JavaBinUpdateRequestCodec do not maintain order of the commands as
serialized in the binary format
[ https://issues.apache.org/jira/browse/SOLR-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shalin Shekhar Mangar updated SOLR-1164:
----------------------------------------
Fix Version/s: 1.5
> 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
> Fix For: 1.5
>
> 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.