[ https://issues.apache.org/jira/browse/SOLR-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209552#comment-15209552 ]
Ishan Chattopadhyaya commented on SOLR-8889: -------------------------------------------- bq. Internally Solr should broadcast to all the shards if there is no composite key prefix. I remember wanting to do this in SOLR-5890, but we took a conscious decision not to, in that issue. Please see: https://issues.apache.org/jira/browse/SOLR-5890?focusedCommentId=14264553&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14264553 > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org