lucene-solr-user mailing list archives

For the search results we actually put the small amount of data in the core.
Once someone clicks the results and we need to go to the item to
display the detailed results, we create another core with a stored XML
string field and an ID. The ID is indexable, and the string field is
only stored.
So we have:
productsearch core
product core
This is in production and working fantastic for the last 4 months.
Our index is about 3M records.
On Thu, Jul 5, 2012 at 4:44 AM, Sohail Aboobaker <saboobaker@gmail.com> wrote:
> 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
--
Bill Bell
billnbell@gmail.com
cell 720-256-8076