You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Geoff Bomford <ge...@comformark.com.au> on 2016/11/09 05:22:59 UTC
2.0 _purge returning "not implemented"
I’m trying to purge some documents by POSTing to /db/_purge
The response I am getting is...
{
"error": "not_implemented",
"reason": "this feature is not yet implemented"
}
Is purge meant to be working in 2.0??
Re: 2.0 _purge returning "not implemented"
Posted by Geoff Bomford <ge...@comformark.com.au>.
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: user@couchdb.apache.org
Subject: Re: 2.0 _purge returning "not implemented"
Today there is not, but I\u2019m keenly interested in pursuing this option. It\u2019s
technically feasible \u2014 the full deletion would be done by the compactor \u2014
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 \u201cauto-purge\u201d 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
> <ge...@comformark.com.au> 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: user@couchdb.apache.org
> 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
>
Re: 2.0 _purge returning "not implemented"
Posted by Adam Kocoloski <ko...@apache.org>.
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 <ge...@comformark.com.au> 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: user@couchdb.apache.org
> 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
>
Re: 2.0 _purge returning "not implemented"
Posted by Geoff Bomford <ge...@comformark.com.au>.
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: user@couchdb.apache.org
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
Re: 2.0 _purge returning "not implemented"
Posted by Brian Brown <bb...@scriberule.com>.
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
Re: 2.0 _purge returning "not implemented"
Posted by Geoff Bomford <ge...@comformark.com.au>.
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.
-----Original Message-----
From: Adam Kocoloski
Sent: Thursday, November 10, 2016 00:46
To: user@couchdb.apache.org
Subject: Re: 2.0 _purge returning "not implemented"
Hi Geoff,
Hmm, no \u2026 purge does not work at the clustered database level in the 2.0
release. It looks like we may have failed to document this change beyond the
API response that you got. There are some subtleties in how we have to
manage that operation in a cluster. For example, if you happen to purge a
document while only two replicas out of three are online, the third one may
ultimately get re-propagated to the other two shards at a later date.
I know some folks are working on adding this capability back in to the
clustered API, but until that work lands if you absolutely need to purge
documents you can navigate to the shard-level API on a different port and
execute the purge request there. That\u2019s not for the faint of heart, though.
Cheers,
Adam
> On Nov 9, 2016, at 12:22 AM, Geoff Bomford
> <ge...@comformark.com.au> wrote:
>
> I\u2019m trying to purge some documents by POSTing to /db/_purge
>
> The response I am getting is...
>
> {
> "error": "not_implemented",
> "reason": "this feature is not yet implemented"
> }
>
> Is purge meant to be working in 2.0??
Re: 2.0 _purge returning "not implemented"
Posted by Adam Kocoloski <ko...@apache.org>.
Hi Geoff,
Hmm, no … purge does not work at the clustered database level in the 2.0 release. It looks like we may have failed to document this change beyond the API response that you got. There are some subtleties in how we have to manage that operation in a cluster. For example, if you happen to purge a document while only two replicas out of three are online, the third one may ultimately get re-propagated to the other two shards at a later date.
I know some folks are working on adding this capability back in to the clustered API, but until that work lands if you absolutely need to purge documents you can navigate to the shard-level API on a different port and execute the purge request there. That’s not for the faint of heart, though. Cheers,
Adam
> On Nov 9, 2016, at 12:22 AM, Geoff Bomford <ge...@comformark.com.au> wrote:
>
> I’m trying to purge some documents by POSTing to /db/_purge
>
> The response I am getting is...
>
> {
> "error": "not_implemented",
> "reason": "this feature is not yet implemented"
> }
>
> Is purge meant to be working in 2.0??