[
https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782599#action_12782599
]
Shalin Shekhar Mangar commented on SOLR-1570:
---------------------------------------------
bq. And FWIW: even if Lance has a really compelling reason, i think we should
just commit this patch, resolve this issue, and open a new issue to make
indexed=false ok since it's significantly different from this one
OK, I'll commit this soon.
> 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
> 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.
