Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <1563003981.1242316485665.JavaMail.jira@brutus>
Date: Thu, 14 May 2009 08:54:45 -0700 (PDT)
From: "Jayson Minard (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1162) SolrJ UpdateRequest does not maintain
 order of operations when sending mixed types of changes (updates, delete
 id, delete query, update iterator)
In-Reply-To: <1071324913.1242165706453.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jayson Minard commented on SOLR-1162:
-------------------------------------

Sounds good, didn't like that returned object in the old method anyway...

I'll update the unmarshal and unit test that used that object to ensure it was accurate as well.  

What do you want to do about the deserialization?  I think it was unsafe before in that it looked up the lists by names and made assumptions about the parms being first.  

> SolrJ UpdateRequest does not maintain order of operations when sending mixed types of changes (updates, delete id, delete query, update iterator)
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-1162
>                 URL: https://issues.apache.org/jira/browse/SOLR-1162
>             Project: Solr
>          Issue Type: Improvement
>          Components: clients - java
>    Affects Versions: 1.3
>            Reporter: Jayson Minard
>         Attachments: Solr-1162.patch, 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.