lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Updated] (SOLR-3682) schema should fail hard if uniqueKey field is multivalued
Date Mon, 30 Jul 2012 21:27:35 GMT


Hoss Man updated SOLR-3682:

    Attachment: SOLR-3682.patch
> schema should fail hard if uniqueKey field is multivalued
> ---------------------------------------------------------
>                 Key: SOLR-3682
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 4.0, 5.0
>         Attachments: SOLR-3682.patch
> 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...
> ...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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message