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 carl.bourne@me.com designates
 17.158.236.118 as permitted sender)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Subject: Re: Summary view for Pie Charting
From: Carl Bourne <carl.bourne@me.com>
In-reply-to: 
 <CABvT1DE1rzXWx0qdaYGBAU3U6mxWqhygBJXi2XZ_8XOyersz+w@mail.gmail.com>
Date: Thu, 20 Sep 2012 12:20:21 +0100
Content-transfer-encoding: quoted-printable
Message-id: <8BD62F9F-BA40-4DDE-9D97-499AC3C9AC9E@me.com>
References: <08180A01-8DC0-491C-8976-B75BBB5F95F4@me.com>
 <46CC7BBD-5AEC-449A-9F80-68E1AC4BB047@couchbase.com>
 <2A199735-20B9-4E24-9EF0-1BE43A649075@me.com>
 <CABvT1DE1rzXWx0qdaYGBAU3U6mxWqhygBJXi2XZ_8XOyersz+w@mail.gmail.com>
To: user@couchdb.apache.org

Thanks,

So I'm assuming the only way to to summarise this information is to do 3 =
separate queries and aggregate the results?

> It's this;
>=20
> map:
> function(doc) {
>  emit(doc.date.expire, null);
> }

If I query against the above without a reduce (_count) function it =
returns all documents according to the ?startkey=3D"2012-10-19" and not =
the count which I need to build the pie chart!

Am I understanding you correctly?

Carl


On 20 Sep 2012, at 10:11, Robert Newson <rnewson@apache.org> wrote:

> It's this;
>=20
> map:
> function(doc) {
>  emit(doc.date.expire, null);
> }
>=20
> and there is no reduce function.
>=20
> query with ?startkey=3D"today's date minus 30 days encoded in same
> format as doc.date.expire", and same for 60 and 90.
>=20
> And remember to ensure that doc.date.expire sorts in the right order.
> Perhaps emit it as new Date(doc.date.expire).getTime() or in ISO-8601
> formatted string.
>=20
> B.
>=20
>=20
> On 20 September 2012 08:04, Carl Bourne <carl.bourne@me.com> wrote:
>> Jens,
>>=20
>> Understand!
>>=20
>> So I guess then the only way to do this is using 3 separate queries =
with startkey, endkey for each time period? Then assemble the results =
externally using whatever performed the query?
>>=20
>> Are there any other options?
>>=20
>> Regards,
>>=20
>> Carl
>>=20
>>=20
>> On 20 Sep 2012, at 01:18, Jens Alfke <jens@couchbase.com> wrote:
>>=20
>>> This isn=92t a valid map function, because it=92s not purely =
functional =97 it uses external input in the form of the current =
date/time. So if the map function is run twice on the same document, it =
will not always emit the same output. That=92s not allowed.
>>>=20
>>> In other words, think of what happens if you generate the index now, =
and then query it 90 days from now. The information in the index =
probably won=92t be valid because everything will have expired already, =
right? But CouchDB has no idea the index is time-sensitive, so it=92s =
going to return you the old data anyway. You just cannot put =
time-sensitive data into a map function.
>>>=20
>>> Instead what you should be doing in the map is writing out the =
expiration times of the documents. Then at query time you can see how =
far in the future those are.
>>>=20
>>> =97Jens
>>=20