[
https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780135#action_12780135
]
Hoss Man commented on SOLR-1570:
--------------------------------
bq. The getIndexedField method already does this but it throws an exception
instead of logging a warning.
OH ... right, missed that.
bq. Should we change that and allow un-indexed uniqueKeys (at least
highlighting can still work)?
I don't understand -- highlighting should work fine if you don't declare a
uniqueKey (it just requires you to match up the highlighting sections by
position instead of by key) so if we've already been requiring that uniqueKey
be indexed i'm cool with leaving it that way.
still interested in Lance's use cases though (ie: what advantage there is in
declaring a field the unqiqueKey even if you aren't going to delete/update it
that can't be gained just by having aa regular stored field named "id" or
soemthing)
> 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.
