Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of saboobaker@gmail.com designates
 209.85.212.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANbU6KJQ13H+By1R-tsL81252Z01dpwZBq+4WqyakyMdjqdPZA@mail.gmail.com>
References: 
 <CAEsaxUr7=jDJAd78_dKHjFMFFgN+rvWOCW1ORJiEWj5TXLHLTg@mail.gmail.com>
	<4FF52612.5030701@elyograg.org>
	<CANbU6KJQ13H+By1R-tsL81252Z01dpwZBq+4WqyakyMdjqdPZA@mail.gmail.com>
Date: Thu, 5 Jul 2012 06:44:08 -0400
Message-ID: 
 <CANAV3WmO0KrGejAhgw-yN1gizy2MfiH-fbFK+C+Apq8OceiNgA@mail.gmail.com>
Subject: Re: Use of Solr as primary store for search engine
From: Sohail Aboobaker <saboobaker@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=e89a8f234d09c36a7a04c412d3d2

--e89a8f234d09c36a7a04c412d3d2
Content-Type: text/plain; charset=ISO-8859-1

In many e-commerce sites, most of data that we display (except images)
especially in grids and lists is minimal. We were inclined to use Solr as
data store for only displaying the information in grids. We stopped only
due to non-availability of joins in Solr3.5. Since, our data (like any
other relational store) is split in multiple tables, we needed to
de-normalize to use solr as a store. We decided against it because that
would mean potentially heavy updates to indexes whenever related data is
updated. With Solr 4.0, we might have decided differently and implement the
grids using joins within solr.

We are too new to Solr to have any insights into it.

Regards,
Sohail

--e89a8f234d09c36a7a04c412d3d2--