Remove all objects matching a filter (including geo filters).
This method enables you to delete one or more objects based
on filters (numeric, facet, tag or geo queries).
It does not accept empty filters or a query.
This method should only be used if you cannot get the list of objectIDs you want to delete;
These operations cannot be processed in parallel by the engine.
If possible, use the delete method instead which is significantly more performant.
The delete by method only counts as 1 operation - even if it deletes more than one object.
This is exceptional; most indexing options that affect more than one object
normally count each object as a separate operation.
When sending multiple deleteBy operations, be aware of our rate limit.
You’ll know you’ve reached the rate limit when you start receiving errors
on your indexing operations.
This can only be resolved if you wait before sending any further indexing operations.
Note this is an expensive operation:
when you have more than 100 requests pending, your requests will be throttled.
when you have more than 5000 requests pending, further requests will be ignored.
if needed, these values can be tuned through configuration.
Delete records by filter
$index->deleteBy(['filters'=>'category:cars','aroundLatLng'=>'40.71, -74.01'/* add any filter parameters */]);
A list of request options to send along with the query.
In this section we document the JSON response returned by the API.
Each language will encapsulate this response inside objects specific to the language and/or the implementation.
So the actual type in your language might differ from what is documented.