[jira] Commented: (SOLR-1570) Complain loudly if uniqueKey field is definied but not indexed=true,stored=true,multiValued=false

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

    [ https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779079#action_12779079 ] 

Hoss Man commented on SOLR-1570:
--------------------------------

recent example of confusion...

http://old.nabble.com/java.lang.NullPointerException-at-org.apache.solr.handler.component.QueryComponent.mergeIds%28QueryComponent.java%3A421%29-to26392614.html

> Complain loudly if uniqueKey field is definied but not indexed=true,stored=true,multiValued=false
> -------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-1570
>                 URL: https://issues.apache.org/jira/browse/SOLR-1570
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>
> When loading a new schema, Solr should log some "SEVERE" warnings if the schema uses a uniqueKey field, but that field/type don't match the expected needs of unieuqKey field for most functionality to work (indexed=true, stored=true, multiValued=false) ... that way people won't (have any reason to) be suprised when things break later)

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