couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <>
Subject Re: CouchDB - Open Document Format mega storage
Date Wed, 09 Nov 2011 11:01:57 GMT
The suggestion to use an update notification handler to trigger
copying into a VCS is dangerous, as it is not guaranteed to get all
your changes (consider compaction running while you're doing this, you
could easily miss a revision).

It's better to store all your versions in couchdb itself *in the
current revision*. Either as JSON;

  "old_versions": {
    "1" : {}
    "2":" {}

or by storing old revisions as attachments. The code doing the update
would post a new revision which contains all your versions, and thus
you cannot lose it, no matter when compaction runs.


On 9 November 2011 10:09, Martin Hewitt <> wrote:
> You might want to look at couchdb-lucene, it indexes attachments using Apache Tika, so
if Tika can index .odt files, you'll be able to search them through couchdb.
> Martin
> Sent from my iPhone
> On 9 Nov 2011, at 09:41, Маркевич Александр <>
>>> You may setup update notification handler in CouchDB config and let it
>>> store any document updates within VCS (I've done same task via
>>> mercurial). So you'll reach two goals: use full power of CouchDB to
>>> search data within documents or transform it into various forms and
>>> track all changes in same time using special tool that done it right.
>> This is a better solution than I thought in first!
>> Because this scheme will planned as a part of corporate reporting system,
>> we need to store some hundred/thousand of report in *.odt files. Need to
>> save all changes and have additional functional wich can get CouchDB
>> include fast text search, save another properties about report and many
>> others.
>> --
>> Markevych Alexander.
>> С уважением Александр.

View raw message