lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From agatone <>
Subject Re: Lucene Index file vs. database
Date Tue, 30 Sep 2008 17:23:31 GMT

Thank you for your reply.
I'm just affraid of choosing wrong option for the project and later it would
be harder to change it.

Pozdrav :)

Otis Gospodnetic wrote:
> Zoki,
> A better list to ask this on is java-user@lucene.
> In short, you can really go either way.  Some people feel more comfortable
> storing everything in DB as they trust it more (RDBMS's have been around
> longer than Lucene has), know how to back it up, need data integrity
> (FKs), etc.  Storing relational data in Lucene requires flattening of
> relations and entities.
> Storing everything in Lucene means larger indices, which doesn't
> necessarily affect search speed, but it does mean things like slower
> optimization, more IO on the machine running search, etc.
> I could go on listing various little advantages/disadvantages, but there
> is no ultimate "do this, don't do that" answer.
> Pozdrav,
> Otis
> --
> Sematext -- -- Lucene - Solr - Nutch
> ----- Original Message ----
>> From: agatone <>
>> To:
>> Sent: Monday, September 29, 2008 9:46:59 AM
>> Subject: Lucene Index file vs. database
>> Hi,
>> First I want to apologize if I'm asking something  that was asked
>> already. I
>> tried search, but couldn't find what I was looking for (or I simply don't
>> know how to define the search string for my question).
>> I'm working on a project that has huge database in the background. We
>> decided to use Lucene for "faster" search. Our search works similar as
>> all
>> searches: you write search string, get list of hits with detail link. But
>> there is dilemma if we should store more data into index that's needed.
>> One side of developing team insists that we should use lucene index as
>> somekind of storage for data so when you get hit, you go onto details and
>> then again use lucene to find document that matches the selected ID. So
>> in
>> the end you end with copying complete database tables into the lucene
>> index
>> Other side insists on storing to index only data that is displayed on the
>> search results list and needed for search criteria. When you go onto
>> details, you have the matching ID so you can pickup that row from
>> database
>> by that ID (I also like this better).
>> Can someone please describe drawbacks and advantages of both approaches.
>> Actually can someone write down what's the actual profit, where and when
>> of
>> the Lucene itself.
>> Thank you
>> -- 
>> View this message in context: 
>> Sent from the Lucene - General mailing list archive at

View this message in context:
Sent from the Lucene - General mailing list archive at

View raw message