Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 79853 invoked from network); 28 Mar 2011 11:15:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Mar 2011 11:15:58 -0000 Received: (qmail 4565 invoked by uid 500); 28 Mar 2011 11:15:56 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 4533 invoked by uid 500); 28 Mar 2011 11:15:56 -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 4525 invoked by uid 99); 28 Mar 2011 11:15:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Mar 2011 11:15:56 +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 (athena.apache.org: domain of bchesneau@gmail.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Mar 2011 11:15:51 +0000 Received: by iyf40 with SMTP id 40so5333163iyf.11 for ; Mon, 28 Mar 2011 04:15:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=JAbTyW9CRVKCL3oQ0ksrRPE0M4phihQC4QhN8nhBgnM=; b=dbWo14hKjKt6/AwR8EWHuX7uHu3EWJZMzFfNHRADgPaNoiWSlqxvqxarzZDHRyQgV1 PJthFY+YtdJEjxmlTLeP9cN3ibAxraDWh5PoKzU7sHtk8ItgfrQ8L12OYjZxxW216xNJ YjSg/Ge4RrgxGY/Ja1+R7JHPsgvFDy4q8OF6Q= 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:content-transfer-encoding; b=ORkif9YCm/jvsaFQpitpaehZzuIKrbqgwgfZi0wk2iHXi3vx5KQw6l/Y+h4JYyPrPD 0f8tUOjEl7yQibNatPnkQdU+Jli0kmClg2qCFr12RDjCJv6S21BhuL6BXDaGuCs/2D76 5N1Uqm+D2ruiRix/oT0Spf/RE6A7IQHIrTebs= MIME-Version: 1.0 Received: by 10.231.43.14 with SMTP id u14mr4141563ibe.10.1301310929590; Mon, 28 Mar 2011 04:15:29 -0700 (PDT) Received: by 10.231.34.200 with HTTP; Mon, 28 Mar 2011 04:15:29 -0700 (PDT) In-Reply-To: References: <3D13B027-14D1-4EA6-9751-591173ED57D2@rgabostyle.com> <4AEB3F68-AB89-4EED-A953-8FF1BC59CA0D@supercoders.com.au> <9F98111A-5E6B-479B-A770-A69467C980D4@supercoders.com.au> Date: Mon, 28 Mar 2011 13:15:29 +0200 Message-ID: Subject: Re: Full text search - is it coming? If yes, approx when. From: Benoit Chesneau To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, Mar 28, 2011 at 6:31 AM, Andrew Stuart (SuperCoders) wrote: > It would be good to know if full text search is coming as a core feature = and > if yes, approximately when - does anyone know? > > Even an approximate timeframe would be good. > > thanks > As far as I know there is nothing planned about that feature currently. Can you eventually open a ticket describing the feature you would like. There are some work from basho porting some analyzer in full erlang in riak search that could be interresting. Having a rest api based on couch would be really interresting. ALso for me such implementation should support distruibution across process natively/. - beno=EEt