lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayson Minard (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1162) SolrJ does not maintain order of operations when using an UpdateRequest object to send them in bulk
Date Wed, 13 May 2009 06:32:45 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jayson Minard updated SOLR-1162:
--------------------------------

    Attachment: Solr-1162.patch

First round of patch, changed the UpdateRequest to maintain one list of different types of
request items, then changed XML serialization to keep the same order, and the same for binary
codec.  Then updated the streaming side of the binary update handler to stream all request
types (not just doc adds) and updated the unit test to verify order is maintained both when
streaming or not streaming using the binary codec.

> 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: Bug
>          Components: clients - java
>    Affects Versions: 1.3
>            Reporter: Jayson Minard
>         Attachments: 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.


Mime
View raw message