kronwerk
kronwerk
> It seems OK, but maybe risky that some users lose data by mistake. yeah, I agree about the risk, of course it's possible - that's why this option has...
> I am curious under which scenarios client need this option? why client not call flushdb command explicitly? @kronwerk @hwware pls take a look at previous comment
@valkey-io/core-team could you pls tell if it's available for merging now?
I have a question on this: are there any contras against introducing "eviction-policy" option here? With options e.g. "drop" and "rocksdb" in order to just reuse all existing maxmemory-policies with...
@zuiderkwast some ideas about the implementation are below, pls take a look - in this case we can allow all 7 options, user is allowed to choose any behaviour. Settings...
@NotAmigo hi, LGTM, but definitely need some tests [here](https://github.com/wal-g/wal-g/tree/master/tests_func/features/mongodb) - at least 1 basic positive scenario, but in my opinion it's a rather complex feature and needs 2-3 basic and...
LGTM, pls wait review from Apelsin234@
@xbasel @soloestoy pls take a look, I've dumped my previous similar PR where you were reviewers