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 2017/02/17 23:50:31 UTC
Current Release still 2.0.0
Is the current release still 2.0.0?
Any timeframe on an update?
Any progress on _purge not implemented?
{
"error": "not_implemented",
"reason": "this feature is not yet implemented"
}
TIA
Re: Current Release still 2.0.0
Posted by Geoff Bomford <ge...@comformark.com.au>.
Yes, indeed! That is exactly what I want.
>I think you'll be more interested in the "hard" delete feature ...
>In brief, it means that deleting a document in CouchDB
>eventually leads to full disk space reclamation.
-----Original Message-----
From: Robert Samuel Newson
Sent: Monday, February 20, 2017 02:22
To: user
Subject: Re: Current Release still 2.0.0
2.0.0 is still the latest release.
CouchDB committers got together very recently (see dev@ thread) to discuss
roadmap (3.0 and beyond) but also discussed minor release. The release
engineering team at Cloudant are going to provide some assistance to improve
CouchDB's release processes (automation, quality, etc), so we should see a
2.1.0 as an early part of that effort.
Clustered purge is actually quite hard but it is in development so keep an
eye on the dev@ mailing list. Even when it lands, I think you'll be more
interested in the "hard" delete feature we discussed at length at the
aforementioned couchdb summit. In brief, it means that deleting a document
in CouchDB eventually leads to full disk space reclamation. There's a
careful operation to perform to know when this is safe to do (we need all
indexes and replications to have "seen" the delete) and another careful
operation to actually remove all traces (we'll leverage the clustered purge
work for that).
Hope that helps,
Robert Newson
CouchDB PMC
> On 17 Feb 2017, at 23:50, Geoff Bomford <ge...@comformark.com.au>
> wrote:
>
> Is the current release still 2.0.0?
>
> Any timeframe on an update?
>
> Any progress on _purge not implemented?
>
> {
> "error": "not_implemented",
> "reason": "this feature is not yet implemented"
> }
>
> TIA
Re: Current Release still 2.0.0
Posted by Robert Samuel Newson <rn...@apache.org>.
2.0.0 is still the latest release.
CouchDB committers got together very recently (see dev@ thread) to discuss roadmap (3.0 and beyond) but also discussed minor release. The release engineering team at Cloudant are going to provide some assistance to improve CouchDB's release processes (automation, quality, etc), so we should see a 2.1.0 as an early part of that effort.
Clustered purge is actually quite hard but it is in development so keep an eye on the dev@ mailing list. Even when it lands, I think you'll be more interested in the "hard" delete feature we discussed at length at the aforementioned couchdb summit. In brief, it means that deleting a document in CouchDB eventually leads to full disk space reclamation. There's a careful operation to perform to know when this is safe to do (we need all indexes and replications to have "seen" the delete) and another careful operation to actually remove all traces (we'll leverage the clustered purge work for that).
Hope that helps,
Robert Newson
CouchDB PMC
> On 17 Feb 2017, at 23:50, Geoff Bomford <ge...@comformark.com.au> wrote:
>
> Is the current release still 2.0.0?
>
> Any timeframe on an update?
>
> Any progress on _purge not implemented?
>
> {
> "error": "not_implemented",
> "reason": "this feature is not yet implemented"
> }
>
> TIA