Tell us some more about your setup, particularly: - you mention routing key. Is the collection used with implicit routing or compositeID? - What does adding &debug=query show? - I'm not entirely sure, frankly, how delete by id and having a different routing field play together. The supposition behind deleteById is that the deletions can be routed to the correct leader by hashing on the id field.
Best, Erick On Wed, May 23, 2018 at 6:02 PM, Jay Potharaju <jspothar...@gmail.com> wrote: > Thanks Emir & Shawn for chiming in!. > I am testing deleteById in solr6.6.3 and it does not seem to work. I have a > 6 shards in my collection and when sending query to solr a routing key is > also passed. Also tested this in solr 5.3 also, with same results. > Any suggestions why that would be happening? > > Thanks > Jay > > > > On Wed, May 23, 2018 at 1:26 AM Emir Arnautović < > emir.arnauto...@sematext.com> wrote: > >> Hi Jay, >> Solr does not handle it differently from any other DBQ. It will show less >> issues then some other DBQ because affects less documents but the mechanics >> of DBQ is the same and does not play well with concurrent changes of index >> (merges/updates) especially in SolrCloud mode. Here are some thoughts on >> DBQ: http://www.od-bits.com/2018/03/dbq-or-delete-by-query.html < >> http://www.od-bits.com/2018/03/dbq-or-delete-by-query.html> >> >> Thanks, >> Emir >> -- >> Monitoring - Log Management - Alerting - Anomaly Detection >> Solr & Elasticsearch Consulting Support Training - http://sematext.com/ >> >> >> >> > On 23 May 2018, at 02:35, Jay Potharaju <jspothar...@gmail.com> wrote: >> > >> > Hi, >> > I have a quick question about deletebyQuery vs deleteById. When using >> > deleteByQuery, if query is id:123 is that same as deleteById in terms of >> > performance. >> > >> > >> > Thanks >> > Jay >> >>
