[
https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1570:
---------------------------
Fix Version/s: 3.1
4.0
Correcting Fix Version based on CHANGES.txt, see this thread for more details...
http://mail-archives.apache.org/mod_mbox/lucene-dev/201005.mbox/%[email protected]%3e
> 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
> Assignee: Shalin Shekhar Mangar
> Fix For: 1.5, 3.1, 4.0
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
