[SOLR-3682] schema should fail hard if uniqueKey field is multivalued

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0-BETA, 6.0
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 27/Jul/12 01:17
• Updated: 22/Jan/20 21:32
• Resolved: 30/Jul/12 21:54

Description

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/[e-mail]%3E

...for 4.0, we should hard fail if uniqueKeyField is used nad doesn't mean the neccessary requirements to function properly.

Issue Links

• is related to: SOLR-10305 uniqueKey field store=false will throw null NullPointerException
• relates to: SOLR-1570 Complain loudly if uniqueKey field is definied but not stored=true,multiValued=false