You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jay (JIRA)" <ji...@apache.org> on 2018/05/23 22:47:00 UTC
[jira] [Commented] (SOLR-8889) SolrCloud deleteById is broken when
router.field is set
[ https://issues.apache.org/jira/browse/SOLR-8889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488144#comment-16488144 ]
Jay commented on SOLR-8889:
---------------------------
[~dsmiley], [~ichattopadhyaya]: is there a solution for this issue. I have a multisharded, implicity routing in my setup and also do lot of deletes. Is there an alternative to using deleteById.
Tested in both solr5.3 & solr 6.6.3.
Thanks
> 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
> Priority: Major
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org