couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1141) Docs deleted via PUT or POST do not have contents removed.
Date Wed, 27 Apr 2011 09:49:03 GMT


Robert Newson commented on COUCHDB-1141:

Well, that teaches me not to commit without reading my email.

This is horrible behavior, imo. Since no one knew that this information was preserved other
than Damien  and Chris isn't it safe to assume no one is storing tombstone information deliberately?
Instead, most people are surprised that whatever they post along with their deletion is preserved
forever (but forever invisible).

I think the default should be to clean out, as trunk does, perhaps we add a flag to bypass
it for the case Damien mentions?

> Docs deleted via PUT or POST do not have contents removed.
> ----------------------------------------------------------
>                 Key: COUCHDB-1141
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>         Environment: All
>            Reporter: Wendall Cada
>            Assignee: Robert Newson
>             Fix For: 1.1.1, 1.2
> If a doc is deleted via -X DELETE, the resulting doc contains only id/rev_deleted:true.
However, if a doc is deleted via PUT or POST, through adding _deleted:true, the entire contents
of the doc remains stored. Even after compaction, the original document contents remain.
> This issue is causing databases with large docs to become bloated over time, as the original
doc contents remain in the database even after being deleted.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message