Batching parameters only affect the update operations, so while deletes are relevant, none of the batching parameters will affect the issue you are seeing with TTLs that are only implemented in the back end.
One thing that might help, in the future, is the sweeper functionality, which is currently on the develop branch. This allows you do do deletes in a way that all Riak subsystems are notified. I don't have a timeline for the release of the next version of Riak that includes this functionality, but I can say that "it passes all the tests", FWIW. -Fred > On Apr 5, 2017, at 7:39 AM, Damien Krotkine <dkrotk...@gmail.com> wrote: > > Also, are there any best practises about deleting data from KV and Solr, > especially, is search.queue.batch.minimum taken in account when deleting keys > ? >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
