[
https://issues.apache.org/jira/browse/SOLR-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17160668#comment-17160668
]
Alexander S. commented on SOLR-14668:
-------------------------------------
Well, the ID doesn't change, changes only the composite part. So it's still
possible to lookup using the ID across shards. That was my assumption and what
I was going to try doing myself, as you described. But the implementation looks
awkward to me and not very reliable so I started thinking Solr may be able to
do this job better.
> 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]