lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karsten F." <>
Subject Re: Best Practice for Lucene Search
Date Mon, 02 Feb 2009 13:23:43 GMT

Hi ilwes,

Did you noticed the thread

I think it is usefull for the question about using lucene storage fields
even if you already have the information in DB.

Best regards

ilwes wrote:
> Hello,
> I googled, searched this Forum and read the manual, but I'm not sure what
> would be the best practice for Lucene search.
> I have an e-Commerce application with about 10 mySQL tables for my
> products. And I have an Index (which is working fine), with about 10
> fields for every product. Is it a common way having the same data (title,
> description, tags, paths to pictures, sold_counter..etc) redundant in my
> mySQL DB and in the Index? And everytime I add a product, saving it to
> both? Would it not reduce the performance doing always things twice?
> What would be the best practice? 
> 1) Save it to both index and mySQL DB (as I'm doing right now). 
> 2) Save only searchable fields (title, description and tags) and an
> product_id to index and use product_id to query everything else from DB?
> 3) ..?
> Would be thankful for some hints and your experience.
> Thx,
> ilwes
> p.s. btw. im working with Zend/PHP but this shouldn't have any impact on
> this question

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message