[jira] Commented: (SOLR-1570) Complain loudly if uniqueKey field is definied but not stored=true,multiValued=false

["Lance Norskog (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780838#action_12780838 ] 

Lance Norskog commented on SOLR-1570:
-------------------------------------

bq.  the only purpose for having a uniqueKey field in solr is the deduping and delete by id

There's a third reason: integration with other data stores with a common id. The use case is to search by terms, get ids back, and do joins against another database. Some of these systems have very large data volumes and want to minimise indexing time and disk size.

> 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.