couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1578) migration tool from non-sharded 1.3.0 CouchDB to sharded / merged CouchDB + BigCouch integrated
Date Sat, 27 Oct 2012 11:59:12 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485421#comment-13485421
] 

Robert Newson commented on COUCHDB-1578:
----------------------------------------

the .couch file does not need to be edited. It would just need to be renamed (foo to shards/00000000-ffffffff/foo.12345.couch)
and a doc created in the "dbs" database to point to it.

                
> migration tool from non-sharded 1.3.0 CouchDB to sharded / merged CouchDB + BigCouch
integrated
> -----------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-1578
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1578
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: Database Core
>    Affects Versions: 2.0
>            Reporter: Dave Cottlehuber
>
> The current DB layout in CouchDB & BigCouch are largely similar, but an efficient
and fast method needs to be found for sharding the single-file CouchDB files in preparation
for a robust migration to a fully sharded setup.
> This might encompass any or none of the following:
> - direct manipulation of .couch files (fast, potentially risky)
> - working solely over HTTP API (slow, low risk)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message