couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Anderson (JIRA)" <>
Subject [jira] Commented: (COUCHDB-69) Allow selective retaining of older revisions to a document
Date Sat, 15 Aug 2009 15:18:14 GMT


Chris Anderson commented on COUCHDB-69:

The patch looks good pretty solid.

forget=true is necessary b/c otherwise DELETE would not be idempotent. Deleting once to set
_deleted=true and again to remove from history would wreck havoc in the face of unreliable

My one question is why match on double-deleted leaves and not the Rev's history=true/false
value? Maybe I'm missing something but it seems like you could avoid doing two couch_db:update_doc
calls to forget history, if you just looked at the history value during compaction.

> Allow selective retaining of older revisions to a document
> ----------------------------------------------------------
>                 Key: COUCHDB-69
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>         Environment: All
>            Reporter: Jan Lehnardt
>            Assignee: Paul Joseph Davis
>            Priority: Minor
>             Fix For: 0.10
>         Attachments: history_revs.2.patch, history_revs.3.patch, history_revs.4.patch,
> At the moment, compaction gets rid of all old revisions of a document. Also, replication
also deals with the latest revision. It would be nice if it would be possible to specify a
list of revisions to keep around that do not get compacted away and replicated.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message