? Basically on search on product
> attributes and a second search on the attributes of related accessories?
>
> many thanks,
> Jonathan
>
> From: Robert Stewart [bstewart...@gmail.com]
> Sent: Thursday, October 20, 2011 12:05 PM
>
.com/
>
>From: Jonathan Carothers
>To: "solr-user@lucene.apache.org"
>Sent: Thursday, October 20, 2011 1:23 PM
>Subject: RE: how to handle large relational data in Solr
>
>Actually, that's the root of my concern. It looks like it product will
>av
20, 2011 12:05 PM
To: solr-user@lucene.apache.org
Subject: Re: how to handle large relational data in Solr
If your "documents" are products, then 100,000 documents is a pretty small
index for solr. Do you know approximately how many accessories are related to
each product on avera
10:50 AM
> To: solr-user@lucene.apache.org
> Subject: RE: how to handle large relational data in Solr
>
> 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 un
: how to handle large relational data in Solr
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
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
