Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <19B8884F-7F70-46CF-9842-50E0703C361B@apache.org>
From: Jan Lehnardt <jan@apache.org>
To: couchdb-user@incubator.apache.org
In-Reply-To: <e282921e0803211318o47eeba44k45e593ea8fd34df4@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Working on Lucene
Date: Fri, 21 Mar 2008 16:34:40 -0400
References: <200803211602.56058.sh@widetrail.dk>
 <DB6DC7C3-F8BC-4892-B2F6-E0A3F237B623@apache.org>
 <e282921e0803211318o47eeba44k45e593ea8fd34df4@mail.gmail.com>

Heya Chris,
On Mar 21, 2008, at 16:18 , Chris Anderson wrote:
> On Fri, Mar 21, 2008 at 1:00 PM, Jan Lehnardt <jan@apache.org> wrote:
>> The first time a change notification is sent, that is, when no index
>> has been written,
>> LuceneIndexer fetches all documents from CouchDB and integrates their
>> contents
>> into the search index.
>
> My use case for full-text searching is a little different from the
> process described here. I'd like to be able to use CouchDB's map
> functions to create views, and run full-text searches against the view
> keys. Eg: I'd like to search just across, say, the titles of any
> documents which have a title attribute.
>
> Will this be supported? Perhaps I am just missing something - it seems
> possible to configure Lucene to run a view-like function on the
> document before indexing. But to me it seems that view keys are an
> ideal way to set up an index for full-text searching.
>
> Just a couple of cents from my application's perspective.

Thanks for the input. This is actually an implementation detail of
the Indexer, but I agree that this should be supported. I also think
we should have some standard way here so other search solutions
can be plugged in without breaking things.

Ideas are welcome.

Cheers
Jan
--