[
https://issues.apache.org/jira/browse/SOLR-15291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309533#comment-17309533
]
ASF subversion and git services commented on SOLR-15291:
--------------------------------------------------------
Commit 507f79158458c450e1f3d2e8ad6ab3e1c3902403 in solr's branch
refs/heads/main from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=507f791 ]
SOLR-15291: ref-guide note clarifying 'safe' way to do De-Duplication
w/SignatureUpdateProcessorFactory in SolrCloud
Include test case demonstrating this works
> 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: [email protected]
For additional commands, e-mail: [email protected]
