I would not recommend removing your relational database altogether. You should treat that as your system of record. By replacing it, you are forcing Solr to store the unmodified value for everything even when not needed. You also lose normalization. And if you ever need to add some data to your system that isn't search-related, you have no choice but to add it to your search index.
Brandon Ramirez | Office: 585.214.5413 | Fax: 585.295.4848 Software Engineer II | Element K | www.elementk.com -----Original Message----- From: Jonathan Carothers [mailto:jonathan.caroth...@amentra.com] Sent: Thursday, October 20, 2011 10:12 AM To: solr-user@lucene.apache.org Subject: how to handle large relational data in Solr All, We are attempting to convert a fairly large relational database into Solr index(es). There are ~100,000 products with ~1,000,000 accessories that can be related to any number of the products. So if I include the search terms and the relationships in the same index, we're looking at a pretty huge index. If we break it out into three indexes, one for the product search, one for the accessories search, and one for their relationship, is there a good way to merge the results? Is there a better way to structure the indexes? We will have a relational database available if it makes sense to do some sort of a hybrid approach. many thanks, Jonathan
