[SOLR-8889] SolrCloud deleteById is broken when router.field is set

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.0, 8.10
• Component/s: SolrCloud, SolrJ
• Assignee: Chris M. Hostetter
• Reporter: David Smiley
• Created: 23/Mar/16 19:58
• Updated: 28/Sep/21 20:23
• Resolved: 16/Aug/21 18:10

Description

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.

Issue Links

• fixes: SOLR-12694 JavaBinUpdateRequestCodec fails to restore UpdateRequest.deleteById correctly when '_route_' is specified.
• is related to: SOLR-12694 JavaBinUpdateRequestCodec fails to restore UpdateRequest.deleteById correctly when '_route_' is specified.
• relates to: SOLR-7384 Delete-by-id with _route_ parameter fails on replicas for collections with implicit router
• relates to: SOLR-5890 Delete silently fails if not sent to shard where document was added
• relates to: SOLR-11868 Deprecate CloudSolrClient.setIdField, use information from Zookeeper
• split to: SOLR-15589 DocRouter API needs redesigned to support stricter routing rules