[jira] Resolved: (SOLR-1695) Missleading error message when uniqueKey is field is missing

["Hoss Man (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man resolved SOLR-1695.
----------------------------

       Resolution: Fixed
    Fix Version/s: 1.5
         Assignee: Hoss Man

Committed revision 911228.
Committed revision 911232.

I added an explicit checks for the number of uniqueKey values being != 1 early on in DocumentBuilder.toDocument.  Prior to this, multiple values weren't checked for until the doc made it all the way to the UpdateHandler.

>  Missleading error message when uniqueKey is field is missing
> -------------------------------------------------------------
>
>                 Key: SOLR-1695
>                 URL: https://issues.apache.org/jira/browse/SOLR-1695
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Minor
>             Fix For: 1.5
>
>
> Sometimes users don't seem to notice/understand the <uniqueKey/> declaration in the example schema, and the error message they get if their documents don't include that field is confusing...
> {code}
> org.apache.solr.common.SolrException: Document [null] missing required field: id
> {code}
> ...because they get an almost identical error even if they remove {{required=true}} from {{<field name="id" />}} in their schema.xml file.
> We should improve the error message so it's clear when a Document is missing the "uniqueKeyField" (not just a "required" field) so they know the terminology to look for in diagnosing the problem.
> http://old.nabble.com/solr-1.4-csv-import-----Document-missing-required-field%3A-id-to26990048.html#a26990779

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