[
https://issues.apache.org/jira/browse/SOLR-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163568#comment-17163568
]
Alexander S. edited comment on SOLR-14668 at 7/23/20, 1:38 PM:
---------------------------------------------------------------
I realized that Solr stores the composite part along with ID so even for us
there's no way to remove the old records if we don't know the previous ID,
which we don't actually know. Reindexing the whole collection is a very heavy
operation. It would make sense if Solr stored the composite part separately or
had an option to locate the record without the composite part across all
available shards.
was (Author: aheaven):
I realized that Solr stores the composite part along with ID so even for us
there's no way to remove the old records if we don't know the previous ID,
which we don't actually know. Reindexing the whole collection is a very heavy
operation. It would make sense of Solr stored the composite part separately or
had an option to locate the record without the composite part across all
available shards.
> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
