[
https://issues.apache.org/jira/browse/SOLR-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399838#comment-17399838
]
ASF subversion and git services commented on SOLR-8889:
-------------------------------------------------------
Commit 5c3465eb498551c53dc310e44ae82cb89890ffc6 in solr's branch
refs/heads/main from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=5c3465e ]
SOLR-8889: Fixed various problems in Solr and SolrJ that could cause deleteById
commands with "_route_" information to processed by the wrong shard, and/or
fail when forwarded to replicas from the shard leader.
Portions of this bug and fixes were tracked in SOLR-12694.
> SolrCloud deleteById is broken when router.field is set
> -------------------------------------------------------
>
> Key: SOLR-8889
> URL: https://issues.apache.org/jira/browse/SOLR-8889
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud, SolrJ
> Reporter: David Smiley
> Assignee: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-8889.patch, SOLR_8889_investigation.patch
>
>
> If you set router.field on your collection to shard by something other than
> the ID, then deleting documents by ID fails some of the time (how much
> depends on how sharded the collection is). I suspect that it'd work if the
> IDs provided when deleting by ID were prefixed using the composite key syntax
> -- "routekey!id" though I didn't check. This is terrible. Internally Solr
> should broadcast to all the shards if there is no composite key prefix.
> Some affected code is UpdateRequest.getRoutes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
