Return-Path: 
 <dev-return-32511-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org>
X-Original-To: apmail-couchdb-dev-archive@www.apache.org
Delivered-To: apmail-couchdb-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B3A5E10D4E
	for <apmail-couchdb-dev-archive@www.apache.org>;
 Fri, 28 Feb 2014 09:32:03 +0000 (UTC)
Received: (qmail 9909 invoked by uid 500); 28 Feb 2014 09:32:02 -0000
Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org
Received: (qmail 9519 invoked by uid 500); 28 Feb 2014 09:31:58 -0000
Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@couchdb.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@couchdb.apache.org>
List-Post: <mailto:dev@couchdb.apache.org>
List-Id: <dev.couchdb.apache.org>
Reply-To: dev@couchdb.apache.org
Delivered-To: mailing list dev@couchdb.apache.org
Received: (qmail 9504 invoked by uid 99); 28 Feb 2014 09:31:55 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 09:31:55 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 209.85.192.48 as permitted sender)
Received: from [209.85.192.48] (HELO mail-qg0-f48.google.com) (209.85.192.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Feb 2014 09:31:50 +0000
Received: by mail-qg0-f48.google.com with SMTP id a108so1387591qge.7
        for <dev@couchdb.apache.org>; Fri, 28 Feb 2014 01:31:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=butSpsbePNTu9xwnjeljzq7xrQ2BAbxFV/qV9TmzwMo=;
        b=uMsXDU8KntqrszX7bTeorgNwTct9qA5MdToBMGDrDMKMM+fSBS637aRwv1xT/Xng8U
         3qoQh0xR4X8ZSM6j/nxHAEWl9wuYSw7VXXL3SEBmP8w+cnxMmQNpIqxqBZZ9F+OTJAdV
         Vd6/nC4sMmg3RC30KDaVXbxgRSHVI18hKU8mAJWgr6JZMMU/Gc+h2JKW7RvDs11yOmx6
         u5Ba4peOkchZPSGOiEN4x5aHu7cfWeg08j5yIlsT0ygKdcTUKzcvMAZ8IfVIGs7SZTN6
         9ocunXZY2cLTuWduFu/lvxdNOkK94tQAw2sNFuQ04LTH5QfM7fsogA5wFVB2IWDqLwtN
         MssA==
X-Received: by 10.140.37.47 with SMTP id q44mr1979094qgq.57.1393579889392;
 Fri, 28 Feb 2014 01:31:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.58.195 with HTTP; Fri, 28 Feb 2014 01:31:09 -0800 (PST)
From: Benoit Chesneau <bchesneau@gmail.com>
Date: Fri, 28 Feb 2014 10:31:09 +0100
Message-ID: 
 <CAJNb-9pg+DeDMk+fPxbtmpdnBshvUWM7CsvvCM7gjwdfC=qtrg@mail.gmail.com>
Subject: mem3 and forced db fragmentation?
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Looking at the code of mem3 it seems that all databases are oblgatory
fragmented (sharded). I understand that you can have only 1 shard /
database but then it will be still stored at
`<database_dir>/shard/<dbname>`.

Is there any plan of having non fragmented databases stored in their
own place ie `<database_dir>/<dbname>`  ? Would be interesting when
you want to manage different policies of backup depending on the type
of database (fragmented or not). Which place should I look to make it
happen?

- benoit