Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of simon@cloudant.com designates
 74.125.82.42 as permitted sender)
Date: Wed, 11 Jul 2012 12:01:32 +0100
From: Simon Metson <simon@cloudant.com>
To: user@couchdb.apache.org
Message-ID: <AB73E69AA1034EC7BD17C0D6C0BFAA9B@cloudant.com>
In-Reply-To: <F043A7641F5B42C0AF8A888C4A846627@chillibean.tv>
References: <F043A7641F5B42C0AF8A888C4A846627@chillibean.tv>
Subject: Re: Large key's in views
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4ffd5d0c_6c89b896_92"

--4ffd5d0c_6c89b896_92
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi Rory, =20
I can't see why that would be a problem, I've certainly had views with 5-=
10 elements in the key. I think you'd need to measure it to be sure thoug=
h. =20
Cheers
Simon


On Wednesday, 11 July 2012 at 11:31, Rory =46ranklin wrote:

> We have a tree structure stored in Couch to mimic a filesystem, and I a=
m trying to determine the most efficient way to calculate storage amounts=
 for any node (and below).
> =20
> As each leaf contains its path up to the root node, would it be bad for=
m to emit out the path with a value of the sum of the contained files wit=
hin that node, considering that node depth could be huge=3F (although in =
reality would rarely go more than 20 levels deep, more often would be les=
s than 10 levels)
> =20
> So it could look like this:
> =20
> emit(=5B=226a1b6034bc634e3cf6865da4780c39eb=22, =22d70c3dc615aaa3065e2e=
dd4ecd9af74b=22, =226a1b6034bc634e3cf6865da4780c50ad=22 =E2=80=A6=5D, 500=
30203)
> =20
> =46rom there I can do a startkey/endkey query to get all nodes below a =
certain point and do a reduce to get the total file size.
> =20
> My worry is that they emitted key being very large could be problematic=
, but I guess this would only impact on how much storage the view will us=
e on disk=3F
> =20
> =20
> =20
> =20
> Rory =20


--4ffd5d0c_6c89b896_92--