lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SOLR-1570) Complain loudly if uniqueKey field is definied but not stored=true,multiValued=false
Date Wed, 25 Nov 2009 20:50:39 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shalin Shekhar Mangar resolved SOLR-1570.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

Committed revision 884263.

Thanks!

> 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
>
>         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.


Mime
View raw message