Hey Rhys,
Short Answer: Try using "set": null and not "set": "null".
Explanation: Although I empty fields via XML, I can see a similar problem
in your query that is actually telling the value to be a string "null" and
not the type null. See:
{ "id": "601000", "agent": {"set": "null"} ...
This
Hi Prem,
Using HTTPClient to establish connection and also i am *validating* whether
> the particular document is *available* in collection or not and after that
> updating the document.
Why do you need to validate the particular document before updating.
Atomic updates either update the docume
Looks like a write lock. Did reloading the core fix that? I guess it would
have been fixed by now. I guess you had run the delete query few moments
after restoring, no?
On Thu, 12 Dec 2019 at 21:55, rhys J wrote:
> I was able to successfully restore a backup by specifying name and location
> in
Could you please provide the exact command-line? It would also help if you
could provide an autoscaling snapshot of the cluster (bin/solr autoscaling
-save ) or at least the autoscaling diagnostic info.
(Please note that the mailing list removes all attachments, so just provide a
link to the sn
Hi!
I am using solr 8.3.0 in cloud mode. I have collection level autoscaling policy
and the collection name is “entity”. But when I run autoscaling simulation all
the steps failed with this message:
"error":{
"exception":"java.io.IOException:
java.util.concurrent.ExecutionExc
