You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Chris M. Hostetter (Jira)" <ji...@apache.org> on 2021/03/25 18:32:00 UTC
[jira] [Updated] (SOLR-15291) Test + ref-guide note about "safe"
way to de-duplicate documents in SolrCloud
[ https://issues.apache.org/jira/browse/SOLR-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris M. Hostetter updated SOLR-15291:
--------------------------------------
Attachment: SOLR-15291.patch
Fix Version/s: 8.9
Status: Open (was: Open)
> Test + ref-guide note about "safe" way to de-duplicate documents in SolrCloud
> -----------------------------------------------------------------------------
>
> Key: SOLR-15291
> URL: https://issues.apache.org/jira/browse/SOLR-15291
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Fix For: 8.9
>
> Attachments: SOLR-15291.patch
>
>
> * The only "safe" way to use SignatureUpdateProcessorFactory for de-duplication in SolrCloud is to define the {{signatureField}} to be the same as the unique key field -- ie: let SignatureUpdateProcessorFactory generate the 'id' for each document
> ** We should add a note about this to the ref-guide ASAP for inclusion in the next release
> * There are currently no "cloud" based tests of SignatureUpdateProcessorFactory showing that even this usage works
> ** We should add a basic test of this usage ASAP to future-proof against it breaking
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org