[
https://issues.apache.org/jira/browse/SOLR-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-8889:
-------------------------------
Attachment: SOLR_8889_investigation.patch
Attached is a patch. It does *not* fix the bug, it's a modification to
ShardSplitTest (one of the _very_ few places even testing router.field) to
experiment with observing the behavior. The patch as-is passes but you may
notice the variable numFoundAfterDelById is not 100 - 3 (100 docs - 3 deleted
by id), it's more than that.
> 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
> Attachments: 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
