lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mag Gam" <>
Subject Re: Advantage of putting lucene index in RDBMS
Date Fri, 06 Oct 2006 04:26:06 GMT
I appreciate everyone's responses.

I guess the main advantage of putting lucene's index into a RDBMS is for
flexibility of queries. Personally, I rather use a RDBMS for results than
lucene because I am more experienced with SQL queries than using Java.

Does anyone have a simple example of using FileDocument (,
which includes the following fields:path, modified, and contents? I would
like to try this approach ....


On 10/5/06, Aleksei Valikov <> wrote:
> Hi.
> > As one of the people who asked about placing indeces into RDBMS, I was
> > primarily interested in just storing index in the RDBMS (basically,
> > storing the structures described on this page
> > in the relational
> > DB). The main reason is NOT to be able to perform some magic with
> > joining Lucene and 'pure DB query' results (which, actually, IS useful
> > in some curcumstances, but don't really see a problem of doing it in
> > Java after quering DB and Lucene), but rather avoid the cost of
> > reindexing and associated problems in complex enterprise environments.
> There no problem joining/intersecting Lucene/DB results in the Java layer
> apart
> from performance. Imagine you have 10k results from Lucene and 10k results
> from
> the RDB and you only need results 20...40 ordered by 'name' field,
> ascending
> (which is the usual case). An sql query with join and limit/offset would
> be much
> faster than joining 20k entries in Java.
> > Yet another advantage of storing index in the DB is its 'managability'
> > and 'debugabiliy' (nice word!). Through there is Luke, etc,
> > administrators in big companies do not want to learn many new tools and
> > having smth already familiar to deal with can sometimes be a good
> > argument in favor of product adoption. (BTW, Compass, as Aleksei
> > mentioned, can be the answer to this prayer - meant to check it out long
> > time ago, but haven't got around to it yet. Also, it seems like the
> > project is half-dead. I wonder if it's true...)
> Compass is a lively and active project, we successfully use it in
> production.
> Bye.
> /lexi
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message