Hi Ahmad, Thanks for this. So do we need this:"*&defType=lucene&q.op=OR&fl=Title* at the end?
Also, I'm guessing we will need to install EdgeNGramFilterFactory? Here are the analyzers / filters we currently are using (just the default stuff): *Index Analyzer: *org.apache.solr.analysis.TokenizerChain Details<http://qa.writepublic.com:8983/solr/admin/schema.jsp#> *Tokenizer Class: * org.apache.solr.analysis.WhitespaceTokenizerFactory *Filters: * 1. org.apache.solr.analysis.StopFilterFactory args:{words: stopwords.txt ignoreCase: true enablePositionIncrements: true } 2. org.apache.solr.analysis.WordDelimiterFilterFactory args:{splitOnCaseChange: 1 generateNumberParts: 1 catenateWords: 1 generateWordParts: 1 catenateAll: 0 catenateNumbers: 1 } 3. org.apache.solr.analysis.LowerCaseFilterFactory args:{} 4. org.apache.solr.analysis.EnglishPorterFilterFactory args:{protected: protwords.txt } 5. org.apache.solr.analysis.RemoveDuplicatesTokenFilterFactory args:{} I am not seeing these from your example in a prev email: <tokenizer class="solr.WhitespaceTokenizerFactory"/> <filter class="solr.LowerCaseFilterFactory"/> <tokenizer class="solr.KeywordTokenizerFactory"/> <filter class="solr.TrimFilterFactory"/> <filter class="solr.LowerCaseFilterFactory"/> Perhaps they were not necessary and just a part of your example? Again, thanks for your help. thanks Brad On Fri, May 28, 2010 at 3:43 PM, Ahmet Arslan <iori...@yahoo.com> wrote: > > > --- On Fri, 5/28/10, efr...@gmail.com <efr...@gmail.com> wrote: > > > From: efr...@gmail.com <efr...@gmail.com> > > Subject: Re: Does SOLR Allow q= (A or B) AND (C or D)? > > To: solr-user@lucene.apache.org > > Date: Friday, May 28, 2010, 4:42 AM > > Hi Ahmet, > > > > Thanks again for the feedback. We will be searching several > > fields of each > > object in the index (title, description, tags). The matches > > on keywords need > > to be in any of these fields and there will be no different > > weights. > > Okey after investigating your example website, i think i understand you > now. As a suggestion you are going to display documents, not a particular > field, or keywords. You can do it with my solution. Create two additional > fields with the types i wrote. Copy your title, desc and tag fields into > these fields. Execute the query - on these two field - as the user types. > You will see the same results with your example website. Just don't forget > to use quotes for the field that uses keyword tokenizer. And the () for the > other one. Also default operator OR is required. When the user is typing the > query tap water, your query will be > q=f1:"tap wate" f2:(tap wate) just before the last key stroke. > > > >
