Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <443261419.1256811179395.JavaMail.jira@brutus>
Date: Thu, 29 Oct 2009 10:12:59 +0000 (UTC)
From: "Asmodean (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1529) NullPointerException in
 LogUpdateProcessorFactory.java when deleting by query *only*
In-Reply-To: <22786974.1256725319765.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-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771372#action_12771372 ] 

Asmodean commented on SOLR-1529:
--------------------------------

Just to clarify from our point of view:

What our client using the Solr web application see when it processes a request (... containing more than 8 *byQuery and no *byId) is an exception (we cant differentiate between types of errors or exceptions, we simply get an exception and have to rollback. It might for example look like the following sample code:

PSEUDO-CODE

try {
  while (hasMoreDeletesToProcessFromOurApplication) {
    if (requestBatchMaxSizeReached) {
      break;
    }

    request.deleteByQuery(...)
  }

  request.process(solrServer)
  solServer.commit()
} catch (Exception e) {
  solrServer.rollback();
  throw e;
}

> NullPointerException in LogUpdateProcessorFactory.java when deleting by query *only*
> ------------------------------------------------------------------------------------
>
>                 Key: SOLR-1529
>                 URL: https://issues.apache.org/jira/browse/SOLR-1529
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Asmodean
>             Fix For: 1.5
>
>         Attachments: logger.patch
>
>
> The problem occurs when a RequestUpdate has deletions that are all *byQuery (as opposed to *byId). The variable 'deletes' is in this case never initialized and will cause a NullPointerException in some cases (where the number of deletions are high enough).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.