The usual approach is to de-normalize the tables, so you'd store docs like (all your product data) min_qty, max_qty, price_per_qty
So the above example would have 4 documents, then it all "just works" You have to insure that the id (<uniqueKey>) is different for each, and probably store the product ID in a field other than "id" for this reason. Best, Erick On Fri, Mar 28, 2014 at 10:27 AM, Ajay Patel <apa...@officebeacon.com> wrote: > > > Hi Solr user & developers. > > i am new in the world of solr search engine. i have a complex product > database structure in postgres. > > Product has many product_quantity_price attrbutes in range > > For e.g Product iD 1 price range is stored in product_quantity_price > table in following manner. > > min_qty max_qty price_per_qty > 1 50 4 > 51 100 3.5 > 101 150 3 > 151 200 2.5 > > the range is not fixed for any product it can be different for different > product. > > now my question is that how can i save this data in solr in optimized > way so that i can create facets on qty and prices. > > Thanks in advance. > Ajay Patel. > > > > > > > > >
