Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-1898

Improved reporting of exceptions during indexing

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Recently indexing some data where I had mismatched types going in (schema was an int, I was sending in a float) and got:

      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)
      

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              gsingers Grant Ingersoll
            • Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: