See below: On Thu, Aug 26, 2010 at 10:24 AM, ahammad <ahmed.ham...@gmail.com> wrote:
> > Hello Erick, > > Thanks for the reply. I am a little confused by this whole stemming thing. > What exactly does it refer to? > In your schema file, for the "text" field type, you'll see a line like: <filter class="solr.SnowballPorterFilterFactory" language="English" protected="protwords.txt"/> Which inserts the a stemmer in your filter chain. Stemmers algorithmically reduce words to their root, e.g. running, runs, etc all reduce to run. The reduced term is all that's put in your index. And when you search, assuming it goes through the same analysis chain, your query will look for run too. The analysis admin page is your friend here for understanding how all this goes together. See: <your solr server url here>/solr/admin/analysis.jsp > > Basically, I already have a field which is essentially a collection of many > other fields (done using copyField). This field is a text field. So what > you're saying is to have a duplicate of this field with different > properties > such that it does not stem? > > This is pretty much what I was suggesting, but whether it's appropriate for your situation is up to you. Making a duplicate field may be prohibitive, can't tell without knowing more about your problem space. > When querying, I assume that I will have to explicitly specify which field > to search against...is this correct? > > Yep, or use the dismax request handler, it lets you do this automagically. The dismax request handler is probably the thing you should look at first, it lets you configure searches to look at multiple fields with different boosts... Best Erick > I'm a little rusty on the solr stuff to be honest so please bear with me. > > Thanks > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Matching-exact-words-tp1353350p1357027.html > Sent from the Solr - User mailing list archive at Nabble.com. >