incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-477) Add database uuid's
Date Thu, 03 Jun 2010 00:11:59 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Randall Leeds updated COUCHDB-477:
----------------------------------

    Attachment: db_uuids_v2.patch

Here's a new patch.

I had to change test/etap/160-vhosts.t test to not depend on the length of the db info record
return by a call to /db. I think this is fine since that's not what the vhost etap is intended
to test.

I cleaned up naughty white space issues with the futon tests.

I updated the compaction code to copy the uuid over when swapping the files.

To be sure this all works I ran a test on my own machine where I copied a 0.10.0 database
to my dev couch. Opening it returns a new uuid. Restarting the couch will regenerate a new
uuid until a write of any kind causes the db header to be written (including a compaction)
at which point the uuid persists and tracks the instance.

I also copied an old database, opened it, made an update, and then copied the same old database
again and added .compact to the name. This acts like a partially completely compaction. The
old .compact file is opened without a hitch and the uuid persists after compaction completes.

Looks all good to me, now. Thanks rnewson for realizing that the interaction with compaction
should be checked.

> Add database uuid's
> -------------------
>
>                 Key: COUCHDB-477
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-477
>             Project: CouchDB
>          Issue Type: New Feature
>            Reporter: Robert Newson
>         Attachments: 0001-add-uuid-to-database-on-creation-return-it-in-db_in.patch,
db_uuids.patch, db_uuids.patch, db_uuids_v2.patch
>
>
> Add a uuid to db_header to distinguish different databases that have the same name (for
example, by deleting and creating the same named database).

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


Mime
View raw message