As always, "it depends". Just from a complexity perspective, my first choice is to store everything in one repository.
If I can store everything in Lucene, I'm a happy camper. If I *must* use a database, I'd prefer to store everything there if possible. I only use both if I can't avoid it because of performance or functionality. If I have to use both, I try to put as much into Lucene as possible. That is, enough to completely handle some requests if I can (as Evgeniy outlined). And if I start trying to use my Lucene index to do database-like stuff like, say, a join, I rethink my design <G>.... Best Erick On Fri, Mar 21, 2008 at 1:06 PM, Evgeniy Strokin <[EMAIL PROTECTED]> wrote: > We store all needed fields in Solr, but we have only 20 stored fields out > of 100+ indexed. Our requirements is to show 20 fields after searching, and > when clients are happy with the result (usually after several searches), we > append all others from DB. Of course it takes a while, because our DB is > huge. But Search is very fast. > > > > ----- Original Message ---- > From: Stuart Sierra <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Friday, March 21, 2008 11:59:20 AM > Subject: Survey: How do you store your fields? > > To Solr users: > > I'm curious: do you store everything in a database and just use Solr > for indexing/searching, or do you store everything in Solr so that > your search results come back with context? Or something in between? > (I know if you want highlighting you have to store those fields.) > > At the moment, I'm using Solr without a database, storing all the > fields, which is convenient for search/retrieval but slow for > updating. > > -Stuart >
