[ https://issues.apache.org/jira/browse/SOLR-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339753#comment-15339753 ]
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: https://issues.apache.org/jira/browse/SOLR-1898 > 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(NumberFormatException.java:48) > at java.lang.Integer.parseInt(Integer.java:458) > at java.lang.Integer.parseInt(Integer.java:499) > at org.apache.solr.schema.TrieField.createField(TrieField.java:426) > {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 (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org