Ah oops. Did not realize the original text was missing spaces. Looked
like so many questions that did, I did not recheck the search query.
Go with Erick's explanation for this specific case. And keep my in
mind for input with spaces.
Regards,
Alex.
On Tue, 16 Apr 2019 at 17:48, Erick Erickson
The issue isn’t SoW. What’s happening here is that the query _parser_ passes
my25word through as a single token, then WordDelimiterGraphFilterFactory splits
it up on number/letter changes after SoW is out of the picture. The
admin/analysis page will show you how this works.
By fiddling with the
Thank you for the reply.
I'm using eDisMax, does it use the same parser as the Standard Query Parser
then?
I think this behavior should be documented somehow... it's very confusing and
to be honest I don't even remember how I got to the sow parameter... and I'm
not sure what that means for all
The issue is that the Standard Query Parser does pre-processing of the
query and splits it on whitespace beforehand (to deal with all the
special syntax). So, if you don't use quoted phrases then by the time
the field specific query analyzer chain kicks in, the text is already
pre-split and the ana
To add some information: using "sow=true" it seems to work.But I don't
understand why with "sow=false" it wouldn't work (can't find anything in the
docs about sow interaction with autoGeneratePhraseQueries); and the implication
of setting saw=true.
I've found this:[SOLR-9185] Solr's edismax and
