Chris, James
thanks for bumping this, we are using this internally at 'scale'
(million+ keys). I want this to work for couchdb as we want to give
back for such a great product and support this going forward, so any
suggestions welcomed and we will test and add them to the local github
account with
I want to use it! I just haven't gotten around to it. I was going to try
and test it out this weekend and if I am able, I will certainly report back
what I find.
James
On Fri, Sep 17, 2010 at 5:55 PM, Chris Anderson wrote:
> On Mon, Aug 30, 2010 at 10:58 AM, Norman Barker
> wrote:
> > Bob,
>
On Mon, Aug 30, 2010 at 10:58 AM, Norman Barker wrote:
> Bob,
>
> I can and have been testing the multiview at this scale, it is ok
> (fast enough), but I think being able to test inclusion of a document
> id in a view without having to loop would be a considerable speed
> improvement. If you have
[
https://issues.apache.org/jira/browse/COUCHDB-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-888:
---
Attachment: 0001-fix-OOME-when-compacting-a-DB-with-many-edit-conflic.patch
This patch again
I'm +1 on having a Futon _stats page. We should put nice explanations
of the individual stats in there too so I don't have to look them up
every time!
—Zach
On Fri, Sep 17, 2010 at 3:10 AM, Dirkjan Ochtman wrote:
> Hi there,
>
> I'd like to be able to determine how much disk space the index for
[
https://issues.apache.org/jira/browse/COUCHDB-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Cottlehuber updated COUCHDB-889:
-
Attachment: windows_build_from_source_docs.patch
./INSTALL.Windows does not have enough
improved docs for windows compile from source in INSTALL.Windows
Key: COUCHDB-889
URL: https://issues.apache.org/jira/browse/COUCHDB-889
Project: CouchDB
Issue Type: Improvemen
Hi there,
I'd like to be able to determine how much disk space the index for a
certain ddoc takes. Is there any easy way of doing that?
Relatedly, would it be possible to rejigger the on-disk layout a
little bit to make the filenames easier to understand? For example, we
now have:
/foo.couch
/.f
