[
https://issues.apache.org/jira/browse/COUCHDB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746186#action_12746186
]
Damien Katz commented on COUCHDB-69:
------------------------------------
Some comments about the patch:
It is now storing the information for every edit in the by_seq index. When
there are a lot of edits, this slows things downs a lot during view building as
it now has to read the meta data for every old rev off disk (could be 1000s),
though it's only concerned with the latest rev and it's conflicts.
With history on, we don't delete old entries from the by_seq index. Why when
the old info is now in the new node?:
+ RemoveSeqs = if HistoryEnabled -> []; true -> RemoveSeqs0 end,
During compaction, it will copy the same unchanged binary over and over for
each rev. So document with an attachment that is editted 50 times, but the
attachment is not, it will make 50 copies of the attachment.
> Allow selective retaining of older revisions to a document
> ----------------------------------------------------------
>
> Key: COUCHDB-69
> URL: https://issues.apache.org/jira/browse/COUCHDB-69
> 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, history_revs.5.patch, history_revs.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.
