Interesting solution. Can you then explain to me for a given query: ?q='kloster' OR kloster*
How the "exact match" part of that is boosted (assuming the above is how you formulated your query)? Thanks! Mike -----Original Message----- From: Michael Della Bitta [mailto:michael.della.bi...@appinions.com] Sent: Wednesday, June 27, 2012 11:11 AM To: solr-user@lucene.apache.org Subject: Re: Wildcard queries on whole words Hi Michael, I solved a similar issue by reformatting my query to do an OR across an exact match or a wildcard query, with the exact match boosted. HTH, Michael Della Bitta ------------------------------------------------ Appinions, Inc. -- Where Influence Isn't a Game. http://www.appinions.com On Wed, Jun 27, 2012 at 12:14 PM, Klostermeyer, Michael <mklosterme...@riskexchange.com> wrote: > I am researching an issue w/ wildcard searches on complete words in 3.5. For > example, searching for "kloster*" returns "klostermeyer", but "klostermeyer*" > returns nothing. > > The field being queried has the following analysis chain (standard > 'text_general'): > > <fieldType name="text_general" class="solr.TextField" > positionIncrementGap="100"> > <analyzer type="index"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.StopFilterFactory" ignoreCase="true" > words="stopwords.txt" enablePositionIncrements="true" /> > <filter class="solr.LowerCaseFilterFactory"/> > </analyzer> > <analyzer type="query"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.StopFilterFactory" ignoreCase="true" > words="stopwords.txt" enablePositionIncrements="true" /> > <filter class="solr.SynonymFilterFactory" > synonyms="synonyms.txt" ignoreCase="true" expand="true"/> > <filter class="solr.LowerCaseFilterFactory"/> > </analyzer> > </fieldType> > > I see that wildcard queries are not analyzed at query time, which could be > the source of my issue, but I read conflicting advice on the interwebs. I > read also that this might have changed in 3.6, but I am unable to determine > if my specific issue is addressed. > > My questions: > > 1. Why am I getting these search results with my current config? > > 2. How do I fix it in 3.5? Would upgrading to 3.6 also "fix" my issue? > > Thanks! > > Mike Klostermeyer >
