From user-return-5243-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Mon Jun 22 15:36:47 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 52468 invoked from network); 22 Jun 2009 15:36:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Jun 2009 15:36:47 -0000 Received: (qmail 51104 invoked by uid 500); 22 Jun 2009 15:36:57 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 51040 invoked by uid 500); 22 Jun 2009 15:36:57 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 51030 invoked by uid 99); 22 Jun 2009 15:36:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 15:36:57 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of temotor@gmail.com designates 209.85.218.218 as permitted sender) Received: from [209.85.218.218] (HELO mail-bw0-f218.google.com) (209.85.218.218) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2009 15:36:47 +0000 Received: by bwz18 with SMTP id 18so4167665bwz.11 for ; Mon, 22 Jun 2009 08:36:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=RKjq7nruH5lG+DUhxyP+qt4JpJkX7FiXTNbJrAkHdA8=; b=isRLoNr4J3D2ZcxatTHZOaLHxkaSKSnK2KFTRnJt6p6mnA7sYugoEJbkGI44ezWzPl Q16syFrvT6aDzZKps52buDRiFQ6d5OJodsImFOWQTi4V4kYeLq8NgvgI75vjwdOq2Y0D 173MduEHptft+UNKq8mrgassXvQxz+4udOtRQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=neA03LP8OCdeDPoKBo+pLNNKeJGGraMdVy5nsk66jITpXM/c1LNdSuCT4Q+QyEAhPm V2zUzPlXwhL9ahUIzb7PBAjyfcZ63o/F1f6n0rGkv7yVCpo7+oabze4AbwvoRLUNcCOE 39ZvE8EV72ny8B1zObd8QW+tZ5FXCHua7GmlM= MIME-Version: 1.0 Received: by 10.204.66.135 with SMTP id n7mr6312903bki.155.1245684987484; Mon, 22 Jun 2009 08:36:27 -0700 (PDT) In-Reply-To: <46aeb24f0906220829r408f085bv8de237e58860204f@mail.gmail.com> References: <-8441383996293842423@unknownmsgid> <2d8fb9950906220746u2fb59ab2w6c463cd8732b671a@mail.gmail.com> <46aeb24f0906220829r408f085bv8de237e58860204f@mail.gmail.com> Date: Mon, 22 Jun 2009 19:36:27 +0400 Message-ID: <2d8fb9950906220836r7b0c5556ma9c3a0ed35419469@mail.gmail.com> Subject: Re: CouchDB for logging & file storage From: Sergey Shepelev To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=001636c5a4fb2e5ff9046cf1a32f X-Virus-Checked: Checked by ClamAV on apache.org --001636c5a4fb2e5ff9046cf1a32f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Yeah, but for new queries it would return empty set until all documents are processed, right? This makes debugging new queries a bit tricky. You have to pick unbiased 2-3K documents into separate database, test your queries there while they're fast to build and then use them on big database. On Mon, Jun 22, 2009 at 7:29 PM, Robert Newson wrote: > You can also pass stale=ok if you don't need the latest results from a > view. > > http://wiki.apache.org/couchdb/HTTP_view_API > > B. > > On Mon, Jun 22, 2009 at 3:46 PM, Sergey Shepelev wrote: > > From my poor experience with couch, i think that your task (ever > expanding > > set of data, no updates) is perfect for couch. > > But, you should > > also consider that expanding-only set of data is a good task for > > constant databases too. Though, you would run into a expansive process > > writing a nice querying layer on top of key-value CDB. > > > > You can do basic and somewhat advanced querying with couch, though, full > > text searching is not here. (Again, my knowledge is poor, maybe FTS is > > possible) > > Consider also, that couch indexing is lazy, it doesn't index documents > until > > you ask it a query. > > > > AND, the most difficult (for me) part - query is blocking on indexing. > You > > won't have any results until whole database is indexed. Index results are > > cached, so old documents aren't processed until they changed. But for new > > type of query and database with 300K items you will wait tens minutes to > > hours to get query result. > > > > But you can run a tiny daemon that does query few times a minute so you > > always have fast queries with up-to-date data. > > > > On Mon, Jun 22, 2009 at 6:01 PM, Nitin Gupta < > nitin.gupta@srishtitechnet.com > >> wrote: > > > >> Hi All, > >> > >> > >> > >> I am new to non-rdbms storage systems. I am working on an application in > >> which we need to log different user actions as plain text. I am not of > the > >> opinion to make use of our rdbms for this activity as writing this on a > >> rdbms can be an expansive process. > >> > >> > >> > >> Can I make use of Couch DB for this activity? Also I am looking to store > >> all > >> the attachments or BLOB into some non-rdbms solution. Can I make use of > >> CouchDB here as well. This way I will just have to add one network > >> component > >> to address file storage and logging of user action. > >> > >> > >> > >> I would probably need to show the logged information on the admin > console > >> or > >> some other UI to the users. I hope that I can do basic indexing, > querying > >> etc on the basis of data items. > >> > >> > >> > >> Regards, > >> > >> nitin > >> > >> > > > --001636c5a4fb2e5ff9046cf1a32f--