[
https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779887#action_12779887
]
Shalin Shekhar Mangar commented on SOLR-1570:
---------------------------------------------
bq. Shalin: your patch looks good to me, except that it doesn't warn about the
indexed=false case.
The getIndexedField method already does this but it throws an exception instead
of logging a warning. Should we change that and allow un-indexed uniqueKeys (at
least highlighting can still work)?
> Complain loudly if uniqueKey field is definied but not
> indexed=true,stored=true,multiValued=false
> -------------------------------------------------------------------------------------------------
>
> Key: SOLR-1570
> URL: https://issues.apache.org/jira/browse/SOLR-1570
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> 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 (indexed=true,
> 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.
