[
https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1570:
---------------------------
Description: 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
(stored=true, multiValued=false) ... that way people won't (have any reason to)
be suprised when things break later) (was: 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))
Summary: Complain loudly if uniqueKey field is definied but not
stored=true,multiValued=false (was: Complain loudly if uniqueKey field is
definied but not indexed=true,stored=true,multiValued=false)
> Complain loudly if uniqueKey field is definied but not
> stored=true,multiValued=false
> ------------------------------------------------------------------------------------
>
> Key: SOLR-1570
> URL: https://issues.apache.org/jira/browse/SOLR-1570
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Attachments: SOLR-1570.patch
>
>
> 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 (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.
