Hi,
How can a Riak KV client determine when a certain CRDT update
operation propagated to Solr?
I am aware that Solr gets updated asynchronously from Riak KV. I
scripted the test and this is noticeable - at the moment in my test I
sleep for 2 seconds after updating before searching (or the searc
The current release of global expiry does not support retroactively dating and
removing objects. Only newly written objects get expiry.
The code for retroactively dating objects exists and will be part of a future
release.
Matthew
> On Dec 30, 2016, at 10:30 AM, Arun Rajagopalan
> wrote:
>
Thanks Matthew & Luca
Re: global expiry - will that option retroactively remove objects? That is
remove objects that became "unneeded" before the option was set ?
Same question w.r.t delete_mode
Re: Map / Reduce - I am not sure the delete would remove the tombstone
unless I set the delete_mode to
On 30 December 2016 at 15:06, Matthew Von-Maszewski wrote:
> Greetings,
>
> I am not able to answer your tombstone questions. That question needs a
> better expert.
>
> Just wanted to point out that Riak now has global expiry in both the leveldb
> and bitcask backends. That might be a quicker so
Greetings,
I am not able to answer your tombstone questions. That question needs a better
expert.
Just wanted to point out that Riak now has global expiry in both the leveldb
and bitcask backends. That might be a quicker solution for your frequent
delete operations:
http://basho.com/produ
Hello Riakers
I wonder if there is anyway to delete all tombstones that were left behind
when delete_mode was set to 'keep'
Also how do I estimate how much space the tombstones take ? We have a ton
of large scale and frequent delete operations and I suspect some space is
used by Tombstones. I wou
