Hi Andrew, * store == store the original value of the text/string being indexed * index == do analysis on the original text/string, which typically means tokenization of text and optional filtering/modifying (e.g. removing, stemming) of tokens.
* indexed fields can be searched * fields that are only stored cannot * stored fields can be used for displaying in UI and highlighting * fields that are only indexed and not stored not so much HTH, Otis ---- Solr Performance Monitoring - http://sematext.com/spm/solr-performance-monitoring >________________________________ > From: Andrew Wagner <wagner.and...@gmail.com> >To: solr-user@lucene.apache.org >Sent: Tuesday, April 24, 2012 10:40 AM >Subject: Re: Deciding whether to stem at query time > >I'm sorry, I'm missing something. What's the difference between "storing" >and "indexing" a field? > >On Tue, Apr 24, 2012 at 10:28 AM, Paul Libbrecht <p...@hoplahup.net> wrote: > >> >> Le 24 avr. 2012 à 17:16, Otis Gospodnetic a écrit : >> > This would not necessarily increase the size of your index that much - >> you don't to store both fields, just 1 of them if you really need it for >> highlighting or displaying. If not, just index. >> >> I second this. >> The query expansion process is far from being a slow thing... you can >> easily expand to tens of fields with a fairly small penalty. >> >> Where you have a penalty is at stored fields... these need to be really >> carefully avoided as much as possible. >> As long as you keep them small, the legendary performance of SOLR will >> still hold. >> >> paul > > >
