[
https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780875#action_12780875
]
Hoss Man commented on SOLR-1570:
--------------------------------
bq. There's a third reason: integration with other data stores with a common id.
I dont' understand ... what you're describing makes total sense for why you
want to put those ids into some "myExternalId" field in solr (as a stored
field), but do you have any reason to put "<uniqueKey>myExternalId</uniqueKey>"
into your schema that doesn't already require "myExternalId" to be indexed ?
you can put ids into solr w/o telling it their are uniqueKeys and still use
them for external purposes ... my point was that the only reason to tell solr
about them is for deduing and delete by Id -- both of which require that it be
indexed.
> 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
> 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.
