lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Pearce (JIRA)" <>
Subject [jira] [Commented] (SOLR-1898) Improved reporting of exceptions during indexing
Date Mon, 20 Jun 2016 15:49:05 GMT


Matt Pearce commented on SOLR-1898:

Was this implemented with SOLR-2402? That certainly reports both the field name and document
ID in the log and update response, although the message doesn't actually indicate a NumberFormatException.

> Improved reporting of exceptions during indexing
> ------------------------------------------------
>                 Key: SOLR-1898
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>              Labels: newdev
> Recently indexing some data where I had mismatched types going in (schema was an int,
I was sending in a float) and got:
> {code}
> Apr 30, 2010 3:48:46 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.NumberFormatException: For input string: "0.0"
>         at java.lang.NumberFormatException.forInputString(
>         at java.lang.Integer.parseInt(
>         at java.lang.Integer.parseInt(
>         at org.apache.solr.schema.TrieField.createField(
> {code}
> I think our indexing exception handling needs to add at least two things (we also need
per document handling of errors during batch, but that is covered by SOLR-445, see also SOLR-482)
> 1. If there was an error creating the field, the exception should specify what the field
name is.
> 2. All document exceptions should, if there is a unique key, report the unique key of
the document that failed.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message