Hi Bjarke, It is not multiterm that is causing query parser to skip analysis chain but wildcard. The majority of query parsers do not analyse query string if there are wildcards.
HTH Emir -- Monitoring - Log Management - Alerting - Anomaly Detection Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > On 4 Oct 2017, at 22:08, Bjarke Buur Mortensen <morten...@eluence.com> wrote: > > Hi list, > > I'm trying to search for the term funktionsnedsättning* > In my analyzer chain I use a MappingCharFilterFactory to change ä to a. > So I would expect that funktionsnedsättning* would translate to > funktionsnedsattning*. > > If I use e.g. the lucene query parser, this is indeed what happens: > ...debugQuery=on&defType=lucene&q=funktionsneds%C3%A4ttning* gives me > "rawquerystring":"funktionsnedsättning*", "querystring": > "funktionsnedsättning*", "parsedquery":"content_ol:funktionsnedsattning*" > and 15 documents returned. > > Trying the same with complexphrase gives me: > ...debugQuery=on&defType=complexphrase&q=funktionsneds%C3%A4ttning* gives me > "rawquerystring":"funktionsnedsättning*", "querystring": > "funktionsnedsättning*", "parsedquery":"content_ol:funktionsnedsättning*" > and 0 documents. Notice how ä has not been changed to a. > > How can this be? Is complexphrase somehow skipping the analysis chain for > multiterms, even though components and in particular > MappingCharFilterFactory are Multi-term aware > > Are there any configuration gotchas that I'm not aware of? > > Thanks for the help, > Bjarke Buur Mortensen > Senior Software Engineer, Eluence A/S
