Hi Erick,
Yes, I commented on the ticket ...after finding it during my search for the
issue in the solr JIRA.
Setup:
2 Nodes, 6 shards , 3 shards on each node (no replication)
Collection uses implicit routing.
Just to give some background ... The first time I tried it ...it worked but
then when i
Hmmm, this looks like https://issues.apache.org/jira/browse/SOLR-8889?
And are you the "Jay" who commented there?
On Wed, May 23, 2018 at 11:28 PM, Erick Erickson
wrote:
> Tell us some more about your setup, particularly:
> - you mention routing key. Is the collection used with implicit
> routing
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 behi
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?
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 th
On 5/22/2018 6:35 PM, Jay Potharaju wrote:
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.
If there is absolutely nothing else happening to update the index, the
difference between the t
