Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 76893 invoked from network); 29 Mar 2011 11:50:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Mar 2011 11:50:14 -0000 Received: (qmail 54764 invoked by uid 500); 29 Mar 2011 11:50:13 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 54723 invoked by uid 500); 29 Mar 2011 11:50:13 -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 54715 invoked by uid 99); 29 Mar 2011 11:50:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 11:50:12 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of email.workbench@gmail.com designates 209.85.161.52 as permitted sender) Received: from [209.85.161.52] (HELO mail-fx0-f52.google.com) (209.85.161.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Mar 2011 11:50:05 +0000 Received: by fxm6 with SMTP id 6so157340fxm.11 for ; Tue, 29 Mar 2011 04:49:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:date:x-google-sender-auth :message-id:subject:from:to:content-type; bh=Sjlx6njsVPxO5jlpjMLGWMrgkAHrnE3Fz2PUUyWlyZo=; b=xnxov5viz6oWZ8pu+n25JYnOF4TkH3CXURwPW8XTBwsMSSOAGbHHw4A91HJqynDsyA zNdqsUqlt0ckZxJy5jk2F9WknxLZbsteyE8DxxRd3Tzn0f+e/eF+j7TXpM1CVdkqNu8K 6M80cITqFJNTRkIzm3qa8w6HU9sK9n5xTuctw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=X30VxLEyWWe3sicxXH3kJ57F2v3By7i69ZckJVgjselnRB56oJRqPSEsn9hRqWBWAc VQKstLCHUrVPZlZ/BFiwKMRoPoqjFCDIeTpcjAvCIzUloae6fhAVeA9vxkFfNorssN/O hQqpYrHmJ+LPnhDNlt0XXfTTrnnJfuIP3K8PI= MIME-Version: 1.0 Received: by 10.223.42.89 with SMTP id r25mr5717152fae.89.1301399385159; Tue, 29 Mar 2011 04:49:45 -0700 (PDT) Sender: email.workbench@gmail.com Received: by 10.223.20.23 with HTTP; Tue, 29 Mar 2011 04:49:45 -0700 (PDT) Date: Tue, 29 Mar 2011 07:49:45 -0400 X-Google-Sender-Auth: _glf6p3J3UOOhBZpueYssDlkpW0 Message-ID: Subject: RE: Full text search - is it coming? If yes, approx when. From: Zdravko Gligic To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I have a bit tricky use case of super tagging or rather a somewhat hierarchical docs categorization. Several CouchDB gurus have suggested that I should look at Lucene and such. My problem is hosting because I would most rather go with a cloud solution such as Cloudant and forthcoming (I hope it's still forthcoming) CouchBase. Comparatively, I have very little amount of data - large number of tiny docs that are indexed every which way possible - such that the size of views dwarfs the size of docs. The full-text-searching problem is best illustrated by the full-text-searching hosting state of affairs at Cloudant and CouchBase - the only two commercial companies worth mentioning within the CouchDb community. Neither one uses Lucene out of the box and only Cloudant has their own solution. This means that I could not use a redundancy-performance perfect Master-Master replication that is hosted by both. This is why either full-text-searching needs to become CouchDb's internal first citizen or our hosting friends need to internalize and make Lucene their first class citizen. P.S. I love both but ...