Hoss Man created SOLR-3682:
------------------------------
Summary: schema should fail hard if uniqueKey field is multivalued
Key: SOLR-3682
URL: https://issues.apache.org/jira/browse/SOLR-3682
Project: Solr
Issue Type: Bug
Reporter: Hoss Man
Assignee: Hoss Man
Fix For: 4.0, 5.0
Solr 3.1 stated logging a SEVERE warning if uniqueKeyField field was used, but
was multiValued. This was done only as a log message so users who upgraded and
had old configs where the field was multiValued (or inherited the
multiValueness from the fieldtype) would continue to work, as long as they used
the field properly.
But this is still causing some confusion...
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201207.mbox/%3ccan4yxvcjr5vh9lhyui3pejzwdgbpd9ez5fywbaghcwq+tps...@mail.gmail.com%3E
...for 4.0, we should hard fail if uniqueKeyField is used nad doesn't mean the
neccessary requirements to function properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
