Thanks Adam,
Without Purge and Delete, it's not a good fit for any data that is updated
frequently, I hope these can be enabled fairly quickly.
-----Original Message-----
From: Adam Kocoloski
Sent: Friday, November 11, 2016 10:14
To: [email protected]
Subject: Re: 2.0 _purge returning "not implemented"
Today there is not, but I’m keenly interested in pursuing this option. It’s
technically feasible — the full deletion would be done by the compactor —
but we want to be fairly careful in minimizing the ramifications for
replication if a user configures this option.
My ideal scenario is that we can configure a database to “auto-purge” a
deleted revision during compaction when we know that said revision has been
recorded by every replication peer for which we have a checkpoint record.
Still needs some discussion though.
I agree that without some sort of option to remove the tombstones CouchDB is
not a good fit for a use case where the data has a shelf life of a couple of
days. Cheers,
Adam
On Nov 10, 2016, at 4:54 PM, Geoff Bomford
<[email protected]> wrote:
I don't know?
Is there an option to enable deletion of deleted documents, especially
when there is no replication???
-----Original Message----- From: Brian Brown
Sent: Thursday, November 10, 2016 09:56
To: [email protected]
Subject: Re: 2.0 _purge returning "not implemented"
On 11/09/2016 03:30 PM, Geoff Bomford wrote:
Thanks Adam,
OK, then maybe Couchdb isn't what I'm looking for because I really
need to purge deleted documents.
I'm not using replication, and my data has a life of a couple of days,
maximum. So I have a lot of data coming in, being updated, and then
being deleted. All those old deleted documents are just going to get
in the way.
Is there not still a config option that tells couch not to store old
version of documents whatsoever? That sounds like exactly what you need
in this case...
--Brian
