Hi Danny and Daniel,
Thank you so much for your inputs.
Actually we use deleteByIds, but because we need the CDCR solution to work
for us, we are having issues when we use deleteById. The deleteById logs a
transaction in the transaction logs and that when passed over to the target
site, the CDCR
Seconding that point, we currently do DBQ to "tidy" some of our collections
and time-bound them (so running "delete anything older than X"). They have
similar issues with reordering and blocking from time to time.
On 9 August 2016 at 14:20, danny teichthal wrote:
> Hi Bharath,
> I'm no expert,
Hi Bharath,
I'm no expert, but we had some major problems because of deleteByQuery ( in
short DBQ).
We ended up replacing all of our DBQ to delete by ids.
My suggestion is that if you don't realy need it - don't use it.
Especially in your case, since you already know the population of ids, it
is r
