Re: Strategy for maintaining De-normalized indexes

2012-05-23 Thread Aditya
Hi Sohail, In my previous mail, I mentioned about storing categories as separate record. You should store and index Category name, MainProduct name as separate record. Index ChildProduct name, MainProduct as separate record. When you want the count, 1. Retrieve the main product name matching the

Re: Strategy for maintaining De-normalized indexes

2012-05-22 Thread Sohail Aboobaker
We are still in design phase, so we haven't hit any performance issues. We do not want to discover performance issues too late during QA :) We would rather account for any issues during the design phase. The refresh rate on fields that we are using from master table will be rare. May be three or f

Re: Strategy for maintaining De-normalized indexes

2012-05-22 Thread Tanguy Moal
It all depends on the frequency at which you refresh your data, on your deployment (master/slave setup), ... Many things need to be taken into account! Did you face any performance issue while building your index? If you didn't, rebuilding it shouldn't be more problematic. -- Tanguy 2012/5/22 So

Re: Strategy for maintaining De-normalized indexes

2012-05-22 Thread Sohail Aboobaker
Thank you for quick replies. Can't the ID (uniqueKey) of the indexed documents (i.e. denormalized data) be a combination of the master product id and the child product id ? -- We do not need it as each child is already a unique key. Therefore whenever you update your master product db entry, yo

Re: Strategy for maintaining De-normalized indexes

2012-05-22 Thread findbestopensource
Thats how de-normalization works. You need to update all child products. If you just need the count and you are using facets then maintain a map between category and main product, main product and child product. Lucene db has no schema. You could retrieve the data based on its type. Category reco

Re: Strategy for maintaining De-normalized indexes

2012-05-22 Thread Tanguy Moal
Hello, Can't the ID (uniqueKey) of the indexed documents (i.e. denormalized data) be a combination of the master product id and the child product id ? Therefor whenever you update your master product db entry, you simply need to reindex documents depending on the master product entry. You can ev

Strategy for maintaining De-normalized indexes

2012-05-22 Thread Sohail Aboobaker
Hi, I have a very basic question and hopefully there is a simple answer to this. We are trying to index a simple product catalog which has a master product and child products. Each master product can have multiple child products. A master product can be assigned one or more product categories. Now