lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1570) Complain loudly if uniqueKey field is definied but not stored=true,multiValued=false
Date Thu, 27 May 2010 23:15:39 GMT

     [ 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/%3Calpine.DEB.1.10.1005251052040.24672@radix.cryptio.net%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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message