[
https://issues.apache.org/jira/browse/SOLR-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160655#comment-17160655
]
Erick Erickson commented on SOLR-14668:
---------------------------------------
How do you propose that would be done? How can Solr know when IDs are changing
and when to even look for the old one? You can't, for instance, do an atomic
update on the composite ID.
Presumably when you know the composite ID is changing you know what all the old
IDs look like and can delete them first. Or perhaps delete them after and live
(temporarily) with duplicates. Or have your reindexing program delete-by-id
since it presumably knows the old ID as well as the new one when it's
re-indexing.
delete-by-query is tempting, but it can lock up your cluster for updates (why
is a long story) for a time, so delete-by-id is preferred if possible.
> CompositeID change provokes duplicates
> --------------------------------------
>
> Key: SOLR-14668
> URL: https://issues.apache.org/jira/browse/SOLR-14668
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 8.2
> Reporter: Alexander S.
> Priority: Major
>
> There are cases when Composite ID can change, e.g. for a Product where you
> use manufacturer or country attribute as composite ID and that value changes.
> This results in 2 examples of the same documents being stored on separate
> shards.
> A way to clean up obsolete data from other shards is required.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]