Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Lucene Users List" <lucene-user@jakarta.apache.org>
From: Paul <paul@waite.net.nz>
To: "Lucene Users List" <lucene-user@jakarta.apache.org>
Subject: Re: Mixing database and lucene searches
Date: Tue, 11 May 2004 15:20:56 +1200
User-Agent: KMail/1.6.1
References: <c7pfni$nj5$1@sea.gmane.org>
In-Reply-To: <c7pfni$nj5$1@sea.gmane.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200405111520.56888.paul@waite.net.nz>

Glen Stampoultzis wrote:

> Hi... I have a query screen where most of the fields search a regular
> database but one field searches for text in the body of the document.  You
> could say the database holds metadata about the documents.  Effectively
> this means I have two separate queries going on - a lucene query and a
> database query.  These results need to be combined.
>
> Anyone have any strategies for dealing with this?  I'm wondering whether
> it's better to replicate searchable fields in the lucene index.  This means
> being very careful that updates get done in two places so it is not ideal.

First index your docs with all fields that are queried on, and storing the
db key.For each query check the terms to see if the any non-metadata (Lucene)
query data has been submitted, If so, run a Lucene query, and build a
resultset of keys. If not, go straight to the database and do the same with a
standard db query.

The Lucene returns are then filled in with a database lookup for each doc
in the returned resultset to provide metadata.

Cheers,
Paul.

---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org