[jira] [Commented] (SOLR-8889) SolrCloud deleteById is broken when router.field is set

["David Smiley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209170#comment-15209170 ] 

David Smiley commented on SOLR-8889:
------------------------------------

It seems deleteById given an id prefixed by the route field value (and an exclaimation) doesn't work -- as I experiment with the test.  It probably doesn't work because even though the request will likely get to the right shard, the ID is simply not the wright ID to delete since it's prefixed and not the actual document ID value.

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org